From: Jano Svitok <jan.svitok@...>
Date: 2007-11-17T03:35:38+09:00
Subject: Re: rails incredibly slow (update)

On Nov 16, 2007 5:45 PM, Rick DeNatale <rick.denatale@gmail.com> wrote:
> On Nov 16, 2007 10:13 AM, M. Edward (Ed) Borasky <znmeb@cesmail.net> wrote:
> > Hmmm ... maybe we should get an IRC channel up for hunting this down.
> > I've got some friends who can usually nail something like this in less
> > than an hour if it's a general Windows/laptop issue and not something in
> > Ruby or Rails. I'm still clinging to the hope that it *is* a general
> > Windows/laptop issue.
> >
> > One thing you might try is CodeAnalyst from AMD. I think it works even
> > on Intel processors, at least at the basic level. It will tell you if
> > something is using a lot of *processor* time. If it's I/O, swapping, or
> > some timeout, you won't see anything.
>
> I'd suggest finding an analog to strace for windows. I'm pretty sure
> such a beast exists.

you can start with either:

- PerfMon - will show you bytes/s read/written from/to memory, the
same for disk io
- ProcExp - will show you open files, handles, threads, current call
stack of the threads
- WinDbg - shows call stack, memory, you can set breakpoints in system calls,...
- kdb - for kernel debugging

Jano