On my Windows XP machine, if I run some command intensive operation
using the command prompt, (like a compile - or a ruby program – see
below), then if I try to start another ruby program from
another command
prompt, it will take forever to start (or a long long time). On my
system a 400Mhz system, It takes a 30 seconds for the first print (of
the second program) to come out and > 5 minutes to get past
the require
of fox. Normally it takes about 4 seconds for the app to come up.
I am planning to use Ruby as a GUI application for a hardware
device we
are going to sell and I am worried that the application might
not start
up if someone is doing intensive work (or as in the case below not
really that intensive). Any one have any ideas on what I
could do about
this problem? Also can any one try it on their Window’s machine to see
how it runs or if you get similar results?
What version of ruby are you running? I am running 1.68 (PragProg’s
version). Also any other commentators with slower machines?
···
-----Original Message-----
From: Yura Kloubakov [mailto:yura@opmr.com]
Sent: Friday, July 25, 2003 3:28 PM
To: ruby-talk@ruby-lang.org
Subject: Re: Slow ruby start up on XP
On my Windows XP machine, if I run some command intensive operation
using the command prompt, (like a compile - or a ruby program – see
below), then if I try to start another ruby program from
another command
prompt, it will take forever to start (or a long long time). On my
system a 400Mhz system, It takes a 30 seconds for the first
print (of
the second program) to come out and > 5 minutes to get past
the require
of fox. Normally it takes about 4 seconds for the app to come up.
I am planning to use Ruby as a GUI application for a hardware
device we
are going to sell and I am worried that the application might
not start
up if someone is doing intensive work (or as in the case below not
really that intensive). Any one have any ideas on what I
could do about
this problem? Also can any one try it on their Window’s
machine to see
how it runs or if you get similar results?
On my 1.8 GHz W2K system it takes < 1 sec to show Fox window
when first program is not running and ~3 secs when it is
running.
