Ruby on Unix vs. Windows

ruby-talk
1

Just for to see if it helps, you could add some explicit calls to
GC.start. I can't say what that will do to your performance, however.

Regards,

Dan

···

-----Original Message-----
From: Rick Nooner [mailto:rick@nooner.net]
Sent: Tuesday, August 16, 2005 3:44 PM
To: ruby-talk ML
Subject: Re: Ruby on Unix vs. Windows

On Wed, Aug 17, 2005 at 06:38:30AM +0900, Berger, Daniel wrote:
>
> I suspect mostly the latter, with a little bit of the
former mixed in
> for good measure. I'm pretty sure the GC algorithm is different on
> Windows, though I can't remember the details now.
>

That's what I suspect as well.

> Any chance you could show us the relevant code? Maybe we
could help
> you with the memory footprint in general.
>

I'm afraid that I can't. That's the problem when you work
for a big company. Even though most of my work is in Ruby, I
can share very little of it. I can tell you what it is
though. It's a SIP protocol analyzer and it builds SIP call
flows in memory from snoop files so there is alot of state
that has to be kept resident in memory for each call (and we
are talking about 1000's of simultanous calls and millions of
messages).

Thanks,
Rick

2

The deployed system will run on linux or solaris so testing on windows was just a quick
way to see the performance difference between sparc/intel. Testing on windows has issues
that I didn't expect, though.

In the interest of completeness, I'll add some calls to GC.start on the windows box and
see if I can get the test to complete.

Thanks,
Rick

···

On Wed, Aug 17, 2005 at 06:57:08AM +0900, Berger, Daniel wrote:

Just for to see if it helps, you could add some explicit calls to
GC.start. I can't say what that will do to your performance, however.

--
Rick Nooner
rick@nooner.net