What is the output on each host if the PLTSTDERR environment variable is
set to 'debug'?
I'm thinking there may be uncompiled modules in your collects on
Windows. Setting PLTSTDERR=debug will show what the compiler is working
on during startup (and perhaps other useful things).
On Mon, Dec 22,
On Dec 21, 2014, at 21:02, Neil Van Dyke n...@neilvandyke.org wrote:
Offhand, I don't know why you're seeing such a big difference, then.
Regarding various ways that filesystem is cached in RAM, I consistently see a
big improvement in Racket startup times when there's caching. Maybe
Hi Marc,
On 12/23/2014 7:17 PM, Marc Burns wrote:
What is the output on each host if the PLTSTDERR environment variable is
set to 'debug'?
I'm thinking there may be uncompiled modules in your collects on
Windows. Setting PLTSTDERR=debug will show what the compiler is working
on during startup
BTW, general tip: anyone comparing these kinds of files might want to
use a diff program that does highlighting of a second diff between
diffing blocks. For example, the Ediff feature of Emacs:
http://postimg.org/image/ef0zjh1sh/
Neil V.
Racket Users list:
Hi all,
I'm using 6.0.1 (64-bit)
I'm developing primarily on Windows 7 (just because) but deploying on
Ubuntu Linux (14.04). I've noticed that on Linux the development tools
start up roughly 10 times faster than on Windows and raco make
compilation is about 2 seconds for 15 source files
A few ideas not specific to Racket (pardon if you already thought of these):
* Does the Linux kernel have the files in cache, but Windows does not?
* Are other processes using lots of CPU or disk on Windows?
* Is the Windows system swapping to disk, but Linux one not?
Neil V.
Hi Neil,
On 12/21/2014 3:33 PM, Neil Van Dyke wrote:
A few ideas not specific to Racket (pardon if you already thought of
these):
* Does the Linux kernel have the files in cache, but Windows does not?
When I compile on Linux, typically I have just (or very recently)
uploaded the files via
Offhand, I don't know why you're seeing such a big difference, then.
Regarding various ways that filesystem is cached in RAM, I consistently
see a big improvement in Racket startup times when there's caching.
Maybe you're using SSD? This is typical for my setup:
[~] time racket -e '(void)'
On 12/22/2014 12:02 AM, Neil Van Dyke wrote:
Offhand, I don't know why you're seeing such a big difference, then.
Regarding various ways that filesystem is cached in RAM, I
consistently see a big improvement in Racket startup times when
there's caching. Maybe you're using SSD?
No SSD ... all
