Ok it's a single main now, but I canot reproduce the issue. It's because this is doing all executions serially, while in a web app there is parallel write and queries going on from multiple web requests.
https://github.com/javadevmtl/ignite-for-github With 3,000,000 records inserted the avg query speed is 112000 nanoseconds which seems very acceptable. The code is simple it randomly generates some string to index in the model then it randomly picks a key uses that key to get a string and then executes an SQL query based on that indexed field. 1- Is it possible in the web scenario that there is multiple threads trying to write to the cache at the same time and at the same time to read there some contention of resources? 2- The other idea I have is to convert my model into a key/value type model. This can work but I required far more RAM to do the work. Since i have to store each property of my model as it's own key/value. Any thoughts? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Re-Query-performance-tp1009p1149.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
