> -----Original Message----- > From: trac-users@googlegroups.com [mailto:trac-us...@googlegroups.com] > On Behalf Of Lukasz Szybalski > Sent: Tuesday, July 13, 2010 10:12 AM > To: Trac Users > Subject: [Trac] Re: Trac performance - 200K+ tickets > > > On Jul 13, 11:53 am, Noah Kantrowitz <n...@coderanger.net> wrote: > > Might help if you gave the full command line, stack trace, etc etc. > > The screen is from a top command, trac is installed via modwsgi with > apache2. > > > 'Top' command gives me below pid, how can I find out what program is > the pid running? It seem like each process is calling some python > code that then takes a lot of cpu to run, but I'm not sure where to go > from here.
ps will at least get you the command line. Beyond that you will need to read up somewhat on *nix debugging. gdb can get you a backtrace, and strace can show you what syscalls are being made. You may also want to look at the docs on the Python cProfile tools. --Noah -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
