Hi, It is nothing strange for the __scrt_common_main_seh to be a hot spot as it is C++ program entry point. I took a look on the profiling results you provided and it seems like a lot of time is spent in serialization/deserialization methods. The most hot method is surprisingly InputStream::EnsureEnoughData that actually does nothing except for the simple check. Seems like a branch predictor miss to me. I'll take a closed look at this later.
Other hot methods seems to be related to named fields [de]serialization, so switching to BinaryRawReader/BinaryRawWriter may help. Best Regards, Igor On Sat, Jul 2, 2016 at 7:35 PM, amitpa <ami...@nrifintech.com> wrote: > I will like to add that the CPU sampling in Visual Studio shows that > > JVM.dll is the hottest path, which is expected i guess. > Second is > __scrt_common_main_seh 24.87 0.00 > > Which I am not sure, why is so hot. > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-C-ScanQuery-slower-than-Jav-ScanQuery-by-2x-always-tp6056p6057.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
