Ticket #1565 (closed defect: worksforme)

Opened 7 months ago

Last modified 2 months ago

dev.itmill.com is slow

Reported by: Jani Laakso Owned by: Marko Gronroos
Priority: major Milestone: IT Mill Sponsored Backlog
Component: undefined Version:
Keywords: Cc: joonas.lehtinen@…, mikael.vappula@…
Known Issue description:
Hours estimate: Deadline (dd.mm.yyyy):
Known Issue version (since): Known Issue title:
Hours done: Depends to:
Affects documentation: no
Known Issue workaround:
Affects release notes: yes Contract:

Description

I guess I have to figure this out with Mikael..

Need to check virtual environment and APache config.

Change History

Changed 7 months ago by Jani Laakso

Doing full refresh for http://dev.itmill.com (intranet 1Gb access) takes considerably longer than http://trac.edgewall.org/wiki ("internet")

I suspect it is either Apache or Postgresql configuration.

For couple users this is quite fine, I just wonder what happens with more users. I'd like this get fixed before it is an issue.

Changed 7 months ago by Jani Laakso

We get {{{ [Mon Apr 14 15:42:13 2008] [alert] (12)Cannot allocate memory: apr_thread_create: unable to create worker thread [Mon Apr 14 15:42:13 2008] [notice] Apache/2.2.8 (Debian) DAV/2 SVN/1.4.6 mod_python/3.3.1 Python/2.4.5 configured -- resuming normal operations [Mon Apr 14 15:42:13 2008] [alert] (12)Cannot allocate memory: apr_thread_create: unable to create worker thread }}} on our apache error.log, let's check this out on tuesday Mikael if possible! Should be default apache2 config..

Changed 7 months ago by anonymous

[Mon Apr 14 15:42:13 2008] [alert] (12)Cannot allocate memory: apr_thread_create: unable to create worker thread
[Mon Apr 14 15:42:13 2008] [notice] Apache/2.2.8 (Debian) DAV/2 SVN/1.4.6 mod_python/3.3.1 Python/2.4.5 configured -- resuming normal operations
[Mon Apr 14 15:42:13 2008] [alert] (12)Cannot allocate memory: apr_thread_create: unable to create worker thread

Changed 6 months ago by Joonas Lehtinen

  • status changed from new to closed
  • resolution set to fixed

Server parameters tuned. Now seems to be much more responsive. Please reopen if still needs tuning.

Changed 5 months ago by Matti Tahvonen

  • status changed from closed to reopened
  • resolution deleted

submitting data and timeline sometimes very slow

Changed 5 months ago by Jani Laakso

I've noticed following behavior multiple times

I've done this "test" typically multiple times per week from my home ADSL, cannot figure out why dev main page is sometimes very slow and sometimes it opens a lot faster.

This might be because of openvz or Trac itself (or even our Apache proxy), your guess is as good as mine.

Note that http://trac.edgewall.org has similar tendency, main page may take 20 seconds to open sometimes.

Reporting / browsing tickets is another matter, they may take long time too but that involves a bit harder database action.

Changed 5 months ago by Joonas Lehtinen

  • cc mikael.vappula@… added
  • owner changed from Mikael Vappula to Marko Gronroos
  • status changed from reopened to assigned
  • milestone set to IT Mill Sponsored Backlog

Have you already ensured that frequent SVN rsyncing is not the source of this performance issue?

Reassigning to Marko for closer inspection...

Changed 5 months ago by Jani Laakso

I have not ensured that SVN rsync does not cause issues, but given that main page (to my knowledge) does nothing with SVN => issue is not with rsync.

Again, main page loads very slowly sometimes.

Comments are quite vague from everyone, what I'd suggest is that someone inspects our quality of service by

  • polling periodically (once a minute) http://dev.itmill.com loading time
  • IMO: it can be done from intranet because primary suspect is some kind of configuration / software issue and not an network bw/throughput issue

Note that we already got good tools for inspecting any website quality of service by

  • polling latencies of any website page

Changed 2 months ago by Joonas Lehtinen

  • status changed from assigned to closed
  • resolution set to worksforme

IMO, current performance is acceptable.

Note: See TracTickets for help on using tickets.