For the most recent batch of tests, I just tested from the local machine. I wanted to take network latency out of the question. Plus, I didn't want to monkey with my firewall settings. What I meant in that statement is that Mongrel Cluster is inlikely to be a problem itself as all it does is launch Mongrel processes. It isn't much of a resource-consumer itself. I do, indeed, just have three instances running.
Do you think I'd get significant information testing from a outside IP? On Oct 14, 3:17 pm, Freddy Andersen <[EMAIL PROTECTED]> wrote: > Just so I understand the test box and your browser is on the same > machine? Did you test this from a outside ip too? > > Your config's look correct. What do you mean by this statement: > > "but it just spawns Mongrel instances, so perhaps Mongrel is the > culprit" > > With your config you should have only three mongrel processes running > on ports 8000-8002. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
