[This message was posted by Serg Gulko of <[EMAIL PROTECTED]> to the "4.4 Changes" discussion forum at http://fixprotocol.org/discuss/17. You can reply to it on-line at http://fixprotocol.org/discuss/read/f8c545b8 - PLEASE DO NOT REPLY BY MAIL.]
Hello Jason! Sorry for late replay, maybe you already in coding now:) Anyway... Many vendors now have FIX engines implemented on pure Java. My company most of the time working under heavy loaded applications with very high processing. We have choosed Java and quite happy with it. But this force us increase RAM on producation servers. Right now difference between C++ and Java in network communication and data parsing not significant. FIX not required a lot of math and if you dont have huge amount of algo that need to be implemented - fill free use Java. As for operation systems... IP stack is faster on Linux/Unix comparable with Win32/64. So if you looking for speed processing - look on this OS. Here Java also will be very useful. Serg Gulko AxonSoftware By the way, what kind of FIX engine you plan to use? > Hello, > > Thanks for responding. > > I think I may off topic but this is interesting. > > I am working on market data right now so I have to filter all these data > to do some calculation. > > > as my manager is very c++ guys and would like to know the performance of > java data structure and c++ data structure. > > In this case, I need to use the new operator in c++ since there is > million of data and the stack memory will overflow. > > I was finding the time to insert all these data into map using either > c++ or java. 30-40% of these data was duplicated. It seems to me java > has faster running time. But, anyway, of course, it is CPU based too. > > I need all these market data to read into memory to do some calculation. > > I am using windows XP (Visual C++) > > Back to FIX, i think C++ and java performance should be close enough. > > Like you say, the CPU is fast enough in these day. > > > Most API in the market still written in C++. Definitely, C++ can do more > thing than java. > > I think for FIX, we just need the connection, we need to collect the fix > message, send fix message for the basic. > > I dont see many FIX Engine implemented in Java.... (am I wrong?)most FIX > Engine especially their API is implemented in C++. I guess C++ still > good and powerful... > > Regards, Jason > > > I have not tested what like you did. I just use map so simple to map > > <tag, text>. In C++, you can define the map as _tags, and add in the > > map by _tags[11]="CliOrdID". If you want to retrive, then do value = > > _tags[11]. It is so quick. I just don't know what you try to tested. > > > > I don't use "new" mostly. If you forget to free them up, then there > > will be a memory leak. But you can be smarter. For example, I define > > one FIX object in whole FIX handler for Fix inbpund and outgoing > > message processing. There will no more space waste. > > > > I am think the OS is wrotten by C and C++. C++ is definitly much > > closer to the kernel level. You may compile the Java code, and get it > > optimazed at most lower level. Now a days, the CPU is much powerful. > > The application running fast or slow, all determined by the design. > > The language may not show much difference. I implemented Web based OMS > > by a separate module. My FIX engine FixExpress is a pure FIX session > > level support. I choose C++ is I think it will be a small, multi- > > thread, quick solution. I did not give a second thought. > > > > > > > > Good luck, peng > > > > FT Computer solutions http://www.eptop.com/FIX/FixExpress.htm [You can unsubscribe from this discussion group by sending a message to mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
