Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: AAI-1523
re-indent code with spaces to clean up some checkstyle warnings
for aai-core test parsers (part of 24k lines of output)
Change-Id: I9908650b6fccfca9657b0b2ca75f74dc6b469449
Signed-off-by: Keong Lim <keong.lim@huawei.com>
|
|
Issue-ID: AAI-1523
re-indent code with spaces to clean up some checkstyle warnings
for aai-core test logging (part of 24k lines of output)
Change-Id: I10e558911e8088cdf088f757a62fc4d3a79752c7
Signed-off-by: Keong Lim <keong.lim@huawei.com>
|
|
Issue-ID: AAI-1523
re-indent code with spaces to clean up some checkstyle warnings
for aai-core test introspection (part of 24k lines of output)
Change-Id: I3b5341661be9f7adc73b87eeaf88cc2d911985fa
Signed-off-by: Keong Lim <keong.lim@huawei.com>
|
|
Issue-ID: AAI-1523
re-indent code with spaces to clean up some checkstyle warnings
for aai-core test exceptions (part of 24k lines of output)
Change-Id: Ib577b1b26604e47b75466ff980c7aab0dcebebc3
Signed-off-by: Keong Lim <keong.lim@huawei.com>
|
|
Issue-ID: AAI-1523
re-indent code with spaces to clean up some checkstyle warnings
for aai-core test concurrent (part of 24k lines of output)
Change-Id: I82d2a46eeefa806b8ce433ecc8e373afaac8e0eb
Signed-off-by: Keong Lim <keong.lim@huawei.com>
|
|
|
|
GremlinGroovy shell singleton and groovy builder singleton
were changed from being singleton because we found
that the classes that were dynamically loaded
were never cleaned up by the garbage collector
which caused a huge increase in the memory consumption
for the traversal microservice which uses this
The conversions from singleton was already committed
but the singleton was not cleaned up earlier
Issue-ID: AAI-1811
Change-Id: Ib74d85be4c1053e7b482fa5b89b562b2352ff803
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
Issue-ID: AAI-1811
Change-Id: I307731ee35d8a644ae995c4b372345a7ebeca0a1
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
ListEndpoints.java - added logger along with system.err
Issue-ID: AAI-2062
Change-Id: Icc0953ae8061a068a1dec978d657e40cad49552d
Signed-off-by: Driptaroop Das <driptaroop.das@in.ibm.com>
|
|
|
|
Enhance the code for how the db serializer works
when it comes to dealing with the relationships
For a particular vertex, when retrieving its relationship vertexes
it doesn't need to get all the properties of the relationship vertex
as it only cares about the aai-uri and named properties
so only partially retrieving those props that is needed for relationships
Issue-ID: AAI-1987
Change-Id: I1440c561d187ff180a599a3f52ac5c8715d5c8e3
Signed-off-by: Harish Venkata Kajur <vk250x@att.com>
|
|
Issue-ID: AAI-2003
Change-Id: I9234b6b594e559b58e445a97b78a4658190e6527
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
|
|
Issue-ID: AAI-1900
Change-Id: Ie6fa1338fd88fcd7ce3f3d350277f82b8f90138f
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
|
|
Issue-ID: AAI-1994
Change-Id: Icc9910db0371eeb8289abd4381ae1936a281a5df
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
Currently the findSubGraph is being invoked
and causing additional calls to the database by backing
a tree backed vertex and slowing the performance of GET ALLs
Original intention of both of them was to pre fetch depth 0, 1, and 2
at once so we don't have to get them at each depth but since
that was not done right there is extra amount of time
After the aai-uri migration to ensure all vertexes
have the aai-uri and also to make sure they are unique across graph
we don't need to traverse a vertex to find the parents to build aai-uri
it was done previously when there was no aai-uri to derive the uri of a
given vertex and its not necessary anymore so there would be performance
improvements of vserver when there are a lot of relationships
Currently the edge labels are retrieved for each vertex a
and b and the performance of the GET with relationships will be
propotional to the GET request and how many cousin edges it has
and the more cousin edges there are the more slower the response time
will be as for each cousin vertex its trying to get the edge in between
so the code is modified to only go to the database for the edge label
when there are multiple edge labels (cousin edges) between a and b
If there are only one edge label and its a cousin vertex then we
can use the edge rule to be able to figure out the edge label
Improve PUT on the cloud region by modifying the getEdgesBetween
method which currently was retrieving all the parent
child edges between a and b and then only using the first edge
The traversal itself was too complicated and was costly in terms of
database retrieval and calls and optimized the code to utilize the
edge information so we can modify the query to db at runtime
based on the information provided so when a 10000 vservers under a
tenant adding a new vserver under tenant would be slow because of the
old query performance as it was taking some time there but with this
optimization, its only spending at most a millisecond or 2 in that
method
Also noticed that when a PUT operation takes place, the method
calls the related objects to create a dmaap event which was in turn
calling the findParents and actually utilizing the parents to create the
dmaap event and would spend quite a lot of time here because of the
expensive call of the findParents in this case we need those vertexes
So optimized the code so based on a given vertex, we have the aai-uri
and the newly added metadata uriTemplate to break the aai-uri into
its parent aai-uri and grand parent aai-uri and so forth
With this breakdown, we can get the list of aai-uris which are parents,
grandparents and then use the aai-uri to look them up which is O(1)
lookup time due to the fact they are unique indexes
The time it takes when doing a traversal to find the parents is
propotional to the number of edges but this will be optimistic
Another area which was improved was the json path execution of the
edge rules so when the edge rules get loaded into memory it creates a
document object, it utilizes the jsonpath to query information about
the edge rules but the only thing here is each time it gets called
the query gets invoked and uses jsonpath to retrieve the edge rules when
we can cached them based on the filter so that the user executed and if
the filter is the same as before, the expected edge rules will return
the same
Too much time was spent making the query and retrieving and building the
edgerules
So a cache is a perfect way to optimize this part
Issue-ID: AAI-1987
Change-Id: Ieb8237de3fd31136ceac14bf4a8216a7ab3b7179
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
Issue-ID: AAI-1523
re-indent code with spaces to clean up some checkstyle warnings
for aai-core test auth (part of 24k lines of output)
Change-Id: I634a49d499f5a6605510633ec2ab6069a04cccba
Signed-off-by: Keong Lim <keong.lim@huawei.com>
|
|
Issue-ID: AAI-1523
re-indent code with spaces to clean up some checkstyle warnings
for aai-core test (part of 24k lines of output)
Change-Id: I3b33fbe46458e4f0f3273c48ff9cfb0673ae18f4
Signed-off-by: Keong Lim <keong.lim@huawei.com>
|
|
where on create the values should be
the same but it ends up being different sometimes
Issue-ID: AAI-1832
Change-Id: Ia8cfb75a5812e6b59f8000a820cf3605ab17eb2b
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
Issue-ID: AAI-1831
Change-Id: Ifcadf1caa0f7764c759997f10f3f789b1a702872
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
Issue-ID: AAI-1826
Change-Id: Ifc7122880e2c98888aa6b478cba3f70fb4c62e52
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
Issue-ID: AAI-1463
Change-Id: Ibdd3803dd825342d54dfa1b008f1a8c2d78d6198
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
Issue-ID: AAI-1812
Change-Id: I2542371baf8f33da1ab2ea3b19073b1f1dc870f4
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
|
|
Issue-ID: AAI-1654
Change-Id: I118b0d94099c7f986303fc9dd9e5dae5144b4bbb
Signed-off-by: LaMont, William (wl2432) <wl2432@us.att.com>
|
|
|
|
|
|
Issue-ID: AAI-1726
Change-Id: Ia7fc62d72baefad98d0aa97ffb1f5df1d25693f1
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
|
|
Change-Id: I9c6472923df7ec6a250e3b81c6b5f833b53d5c29
Issue-ID: AAI-1646
Signed-off-by: Mohamed Asgar Samiulla <sammoham@in.ibm.com>
|
|
|
|
Issue-ID: AAI-1678
Change-Id: I2bafe046d5c99e3db63862dd5b1ca1ed2da5135b
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
|
|
Change-Id: I63009b10aec1e1a73348eaeaa536b1a64dcc11b8
Issue-ID: AAI-1662
Signed-off-by: Mohamed Asgar Samiulla <sammoham@in.ibm.com>
|
|
Issue-ID: AAI-1632
Change-Id: I4c52de06f20d1a89ff2403b98af73a89a04467ea
Signed-off-by: Venkata Harish K Kajur <vk250x@att.com>
|
|
Change-Id: Iaf98e45665979d156838d1c7596845108b015cc7
Issue-ID: AAI-1661
Signed-off-by: Mohamed Asgar Samiulla <sammoham@in.ibm.com>
|
|
Issue-ID: AAI-1298
Change-Id: I0a880be136f8ea3c0d780e0f9653006a5d5ebc61
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
|
|
|
|
|
|
Issue-ID: AAI-1632
Change-Id: I4f6c566dcd2737424bcc42642147f912e745b94f
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
|
|
Issue-ID: AAI-1628
Change-Id: I88cc21c2b3233eff34febda18497a5131deb4e05
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
|
|
Issue-ID: AAI-1298
Change-Id: Idc5c6652eb4bf11204f53f88193d0ca0c3b2cf5e
Signed-off-by: Kajur, Harish (vk250x) <vk250x@att.com>
|
|
Change-Id: I16d1fbe7ca03ecd6659161ae9bfbf3d4bd5c59be
Issue-ID: AAI-1610
Signed-off-by: Mohamed Asgar Samiulla <sammoham@in.ibm.com>
|
|
Change-Id: I76ecc0d4e4193be1343afae2906fb179768dbbdb
Issue-ID: AAI-1607
Signed-off-by: Mohamed Asgar Samiulla <sammoham@in.ibm.com>
|
|
|
|
Change-Id: Ifa94277e74486bc2086ce5cad5077d59cdbf0f29
Issue-ID: AAI-1595
Signed-off-by: Mohamed Asgar Samiulla <sammoham@in.ibm.com>
|
|
Change-Id: I52a88526180acde91c6d9818d446e22ce175244d
Issue-ID: AAI-1569
Signed-off-by: Mohamed Asgar Samiulla <sammoham@in.ibm.com>
|
|
Change-Id: I60628cd098911f945042f731b779ec9d49f84ecb
Issue-ID: AAI-1594
Signed-off-by: Mohamed Asgar Samiulla <sammoham@in.ibm.com>
|
|
|
|
|