| And I am sincerely happy you are having NO issues. Really.
I am not just talking about my own experience, but because I answer question on this list alot, and for a few years, I get a lot of email to me off list when people have issues. If it is a simple question, I answer, if not, they can hire me to consult.
When it is OS X, it usually turns into a bang your head against the wall fest. With windows, it has been much easier to find a problem and resolve, and I get much less of these types of stability issues with windows.
IMHO, it is the software that should drive the decision, not the hardware. All of my servers, are dedicated to a specific purpose. What does witango run best on? What does my database server run best on? The answer is not always the same. Witango runs on Windows the best, in my opinion, but my database server kicks *ss over running on windows on linux. So my db servers run on Fedora Core 4.
Again, in my experience, the answer usually has to do with how the software manages multiple threads. Does the software use Native OS Threads? or does the software run as if it is only one thread, and does threading of processes internally? If the software does not use Native Windows Preemptive Threading, you are almost always better off with a *nix operating system. I have seen the windows process scheduler choke these types of one thread apps, not allowing them to "Breathe". Where under *nix, they excel.
Why do apps go with internal threading? Just ask witango inc how fun it is to maintain a codebase that has to implement threads completely differently based on the OS. And then discovering that certain methods do not function well within a thread, or not THREADSAFE. Its a pain in the *ss. I believe this was much of the woes with witango on v5, and pre 10.4.
So you determine, the software will run better on *nix than windows. The clear choice would have to linux, with NO gui. It will scream, and be more reliable that OS X. It has to be. Just do an experiment, on linux, and load KDE on your server, and VNC for a week. Then don't load the gui, and no vnc, just use ssh to get in. You will see a big difference in resources used and stability, usually. I guess you could just load the open source darwin build. Not to mention, whatever software you are using, most likely will have been hammered and debuged more on windows, and linux before os x.
Last, if you really like the OS X gui on your server, and all hte resources that uses, and you are comfortable with it, and it is easy for you to administer, and you are not having issues, don't fix what ain't broke.
--
Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 On Nov 15, 2005, at 12:53 PM, Jon van der Raadt wrote: Well, I could not agree with you all less...
We moved our site off of Solaris because of the costs of the hardware/software (both Witango and Oracle). Moved to Mac OSX 18 months ago and have had no issues either with Witango or MySQL.
We are not using the XServe as that experiment (original G3 XServe) went badly...
Jon On 15-Nov-05, at 1:28 PM, John Muldoon wrote: Robert, Couldn't agree with you more. I moved everything from Mac to Windows. I also kicked and screamed the whole way. But I gotta tell you, the difference in stability and upward extensibility is huge. And like it or not, almost everything is built around Windows, even if it isn't Windows itself.
It was a very difficult thing for me to go to windows. I went kicking and screaming. I went from Tango2000 for the mac, to Witango 5 for windows. But after all this time, it was definitely the best decision.
And more recently, because of all the bandwidth I use at my colocation center, I had the opportunity to get several XServe G5 DP machines to use free, or for almost nothing. It was a sponsorship kind of thing. I would then have to write up, and give testimonials and such. So did a bunch of testing on windows and mac. I still chose windows, and then proceeded to upgrade all of my windows hardware for my cost. And I would have LOVED to have gone to the XSERVEs. Cuz I think they are cool, and I love the mac.
Also, in Witango 5.5, they completely rewrote the code that handles db connections and such. And in 5.0, this was the area that caused any instabilities I saw in 5.0. I posted a very long message about my testing with v5.5, under load, regarding this major change.
I do understand your frustration, but I think this was an evolutionary change, and not a bug fix. I upgraded 4 machines and bought 2 more licenses. It was well worth it. My sites don't go down, although I have seen a cache issue, that I am still trying to reproduce.
Unfortunately, I am slowly moving off witango, for many reasons, most previously posted. It will take me most of 2006 to complete the move, though. Until then, 5.5.009 on windows is a VERY stable platform. But don't get me started on the dev studio, and documentation for things like java beans.
For a server platform, with every experience I have had, with many pieces of software, linux or windows is always a better choice than os x. I would move completely to linux, but I would have to do more testing with witango for linux. But is it even done for 5.5? As recently as a few weeks ago, it listed licenses for linux as PRESALE. What is the status on that? Anyone know?
Just a footnote, one other big reason for witango on windows, vs mac or linux, is extendability. There are by far more methods to connect to other services, like payflowpro, and other stuff like that through windows.
--
Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 On Nov 15, 2005, at 10:43 AM, Andrew Derry wrote: On a side note, to Robert - I would have gone windows all the way in the first place if it'd been up to me. It's the people that own and maintain (the non-technical side of) the server are Mac all the way so wouldn't have any of that. ;)
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
|
