Re: Weird performance issue


On Apr 27, 2009, at 21:20 , court3nay wrote:

I ran a profile, too.

looking at your profile on fast and slow shows a ton of differences.
If I ignore the times completely I find this very interesting cluster
at 14 calls on your slow run: http://pastie.org/463189.txt

Basically, it looks like you're not loading any gems on the fast side
at all, despite having roughly the same number of requires. You don't
have any calls to gem_original_require on the fast side for example.
At this point I suspect the fast side is more incorrect than the slow
side, but I dunno.

So, look at `gem env` on both sides, look at `env | egrep "GEM|RUBY"`.
Compare the two and see if you find anything... I think the
suggestions to look at the system with dtrace and the like are going
way too deep way too fast. It's like trying to drink from a firehose.

.

Relevant Pages

  • Re: Quorum size for Windows 2003 SP1
    ... Usually, with tons of Shares and PRINTERS, the quolog file (circular file, ... We do have a ton of share and printers on the cluster. ...
    (microsoft.public.windows.server.clustering)
  • Re: New User Profile
    ... > Documents and Settings in Explore the profile is not there. ... > setup a ton of users and this is my first encounter with this problem. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: GAL nach Migration E55 -> E2K3
    ... Die Migration der Clients und Profile steht noch aus. ... Die Benutzer und Gruppen bzw. Kontakte und Verteilergruppen wurden in eine eigens angelegte OU kopiert. ... der "Berater" hat dann den Cluster auch gleich geliefert ?. ... Frank Carius MS Exchange MVP ...
    (microsoft.public.de.german.exchange2000.setup.installation)
  • Re: Profiling Servlets and JSPs
    ... The only thing JProbe couldn't do is profile a cluster. ... processes running JVM. ... darrell dot grainger at utoronto dot ca ...
    (comp.lang.java.programmer)
  • Re: Quorum size for Windows 2003 SP1
    ... We do have a ton of share and printers on the cluster. ... >> MOM 2005 is telling me that The log file quolog.log exceeds its maximum ...
    (microsoft.public.windows.server.clustering)