phpScheduleIt
May 24, 2013, 03:38:33 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: phpScheduleIt 2.4.2 has been released!
 
   Home   Help Login Register  
Pages: [1]
  Print  
Author Topic: schedule takes too long  (Read 6962 times)
jetsaredim
Newbie
*

Karma: 0
Posts: 5


« on: May 22, 2006, 01:25:18 PM »

I've had a number of complaints from people that use the scheduler I setup takes too long to schedule anything.  The amount of time that it takes between when you click submit on the scheduler window till when it refreshes can be up to 5 minutes or more.  I'm assuming that I have something configured incorrectly, but I'm not sure what.  Eventually, it does come back and it gets updated with the correct information, but it just takes a while.  Is there any way to get some debug information out of the scheduler, so that I can properly diagnose the problem and fix it?

Thanks...
Logged
Nick
Administrator
Hero Member
*****

Karma: 15
Posts: 5419


WWW
« Reply #1 on: May 23, 2006, 09:46:21 AM »

Is this only happening on IE, by any chance?
Logged
jetsaredim
Newbie
*

Karma: 0
Posts: 5


« Reply #2 on: May 23, 2006, 11:48:01 AM »

Actually, I don't think there are many, if any - maybe 1 or 2, that use IE in the group of about 30 users.
Logged
Nick
Administrator
Hero Member
*****

Karma: 15
Posts: 5419


WWW
« Reply #3 on: May 23, 2006, 01:29:04 PM »

Can you estimate how many days and resources you are showing?  Starting in version 1.1, every cell became clickable (which added a huge amount of code to be rendered).  On very large schedules, this ends up taking a long time.

Also, if you view the source on your schedule page, near the bottom there will be something that says "Schedule printout time".  Can you post that?
Logged
jetsaredim
Newbie
*

Karma: 0
Posts: 5


« Reply #4 on: May 23, 2006, 01:44:14 PM »

I'm not explaining the problem correctly.  Its not taking a long time to print the schedule correctly.  

The schedule page itself only takes about 30 seconds to print, which is pretty fast considering there are about 11 resources at about 70% capacity being shared by about 30 people at different times - with a full week showing at at time.  (We're using this tool as a way to schedule time on test machines, rather than meetings in conference rooms.)

The problem is that when you are in the little pop-up that allows you to enter details of a meeting and you then click save, it takes a long time to get the scheduler to acknowledge that you scheduled something and refresh the page with the "close" link.  Does that make sense?
Logged
Nick
Administrator
Hero Member
*****

Karma: 15
Posts: 5419


WWW
« Reply #5 on: May 23, 2006, 02:25:20 PM »

Ah, understood.  Are you repeating the reservation many times?  How long is it taking to confirm the reservation?
Logged
jetsaredim
Newbie
*

Karma: 0
Posts: 5


« Reply #6 on: May 23, 2006, 02:54:40 PM »

I don't think that anyone is even using the repeating feature - doesn't really apply.

The length of time for the ack is at least two-three minutes.  I mean, this isn't a terribly slow box - its a P4 with 1GB of memory, so it shouldn't take that long.  And I readily admit that its probably a config error on my part, but I don't know how to debug the scheduler to see what's actually taking all of that time.  Is there any way to enable status messages to get printed in real-time while its applying the reservation or something?
Logged
jetsaredim
Newbie
*

Karma: 0
Posts: 5


« Reply #7 on: June 13, 2006, 03:06:02 PM »

I think I figured out what is taking so long.  I was looking around in the config.php settings and noticed that my mail settings were set to mail instead of smtp.  I changed the setting back to smtp and now the page reloads quick, but it timesout on connecting to the smtp server.  So, my guess is that the problem was that the mail was taking too long.  Is there any way to figure out what actually is specifically taking so long?
Logged
Nick
Administrator
Hero Member
*****

Karma: 15
Posts: 5419


WWW
« Reply #8 on: June 13, 2006, 05:59:41 PM »

You can add echo statements in the code at locations you think may be hotspots.  Without a profiler, though, I don't know of any other way.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2006-2007, Simple Machines Valid XHTML 1.0! Valid CSS!