-
January 19th, 2015, 02:09 PM
#4
The results from the VisualVM are quite puzzling, because they don't mention other methods invoked beside the two marked as hot spots;
and also because the first one is a two-line-long final method that I expected to be expanded inline by the JVM.
But, indeed, they spot an operation that is likely to be involved in this CPU problem; and it is not easy to fix it.
Actually, your usage of the COMMAND mode, by sending thousands of real-time ADD events in a loop, is a use case that was not expected and was not optimized properly.
You could resort to the snapshot case and send the events that make up a search result as part of a snapshot.
This means that you cannot have a persistent subscription on which to send the search results, but that you have to perform a one-shot subscription for each search, so that you can leverage the snapshot for the answer.
The snapshot in COMMAND mode is handled in a different way that does not involve the reported bottleneck.
Similar Threads
-
By shabbirh in forum Client SDKs
Replies: 1
Last Post: April 23rd, 2013, 09:27 AM
-
By ulises.juarez in forum General
Replies: 3
Last Post: July 29th, 2011, 08:56 AM
-
By veloearl in forum General
Replies: 1
Last Post: February 22nd, 2008, 09:23 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 11:04 PM.
Bookmarks