Well, very slightly in its defense it did have to create a couple thousand new rows... yeah, who am I kidding, the thing is pokey.
Me and a partner are trying to get this thing in shape, but neither of us are ruby / webserver gurus. We realize something isn't working quite right here and while we are looking to get mongrel clustering going + this is going to be load balanced between 2 machines, there is something else going on. Until we figure out what it is, extra hardware won't really solve the problem. for my testing, I'm pointing to a specific machine, and only have a single mongrel processor going. Expanding on what I posted earlier its a suse 10 enterprise machine, we had to setup the ODBC connection to MS sql server using free tds and I think there might be one other kludge used in there. My buddy was the one who got the servers talking, but I think its pretty much a stock install from the gems. I'll double check if there was much else done to these machines. regardless, do you have any other suggestions on where we might look to either see what problems are occurring, or tuning suggestions? With the current setup we are not able to leave the MS Sql environment, so some of this is here to stay. Bob -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
