D
dbeavon
Guest
As far as the GUI point goes, yes, there are server and desktop versions of windows. For the OE dbms you would probably want to run on a *server* version of windows in production. You also want to disable all the "bells and whistles"; turn off DEP, and set your virus scanning exclusions, and disable offline files in the sync center, etc. It would be very important to disable all the "unnecessary" security overhead to put the two platforms on a level playing field. Beyond that I would need to see specific evidence to believe Linux is faster in a given scenario. I'd guess it depends primarily on the specific app in question, and on the related developers. Most applications developers would probably optimize for the platform they use every day and then port things to the others (or let some other outsource developer do that part of the work). I must say that this is one thing that is so painful about HP-UX. Nobody is optimizing for HP-UX anymore. The bar is low - it either works, or you don't get to check that box. HP-UX is not going to be the focus for any performance optimizations. David PS. It's not hard evidence of anything, but I wanted to tell a Windows vs Linux story of my own. In one case I believe I had observed that Progress had done their initial software development on Windows and then ported to Linux/UNIX, overlooking a performance degradation. Here is the KB. knowledgebase.progress.com/.../State-Free-AppServer-Calls-on-UNIX-Linux-May-Perform-Poorly . The repro I used when I reported this case was quite basic. It involved making a number of simple appserver calls in a tight loop with a prodataset. Given the overhead (an extra ~50-100 ms per round-trip) I don't think it is something a software developer would overlook if it happened on a platform they used every day.
Continue reading...
Continue reading...