phpgroupware-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Phpgroupware-tracker] [Bug #1192] MYSQL raise 50% CPU and httpd 45% wh


From: nobody
Subject: [Phpgroupware-tracker] [Bug #1192] MYSQL raise 50% CPU and httpd 45% when asking 2000 tickets
Date: Mon, 16 Sep 2002 19:25:45 -0400

=================== BUG #1192: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1192&group_id=509

Changes by: Dave Hall <address@hidden>
Date: 2002-Sep-17 09:25 (Australia/Melbourne)

            What     | Removed                   | Added
---------------------------------------------------------------------------
            Category | None                      | tts




=================== BUG #1192: FULL BUG SNAPSHOT ===================


Submitted by: sebmay                    Project: phpGroupWare                   
Submitted on: 2002-Sep-13 07:20
Category:  tts                          Bug Group:  0.9.14 RC3                  
Severity:  5 - Major                    Priority:  High                         
Resolution:  None                       Assigned to:  None                      
Status:  Open                           Component Version:  None                
Platform Version:  Linux - Mandrake     Reproducibility:  Every Time            

Summary:  MYSQL raise 50% CPU  and httpd 45% when asking 2000 tickets

Original Submission:  In general in 14RC3, when you try to get lot of records, 
you notice an horrible response time.
What is lots : 2000 tickets for example.
On Linux, asking 2000 records to Mysql is just a snap. But when you ask 
PhpGroupware to show all tickets (closed and open) and you have 2000 of them, 
you simply pass the 30 seconds and get rejected by PHP. We will not increase 
this tempo : Just create 1000 contacts in the address book. Try to display them 
one shot....and get crazy.

My question : Is this solved in the .14 release ?

If not : It seems that you do like asking all records with an individual Mysql 
select ! Or you may read all of them one shot, but then get some linked 
information in another file one after the other... Like 2001 connection and 
selects.
Then better load all linked info in one table, then read all selected records 
in one select, and then do the links with PHP reading memory indiced table.

Please do the following test : create a big base ! Create 10 000 contacts ! 
then travel down the base...

Every guy using the addressbook does it because : he got a large amount of 
contact, and they are many guys to share the contacts. If it is not the case, 
they use the integrated address book of theire local outlook/netscape etc...

Briefly : reading into Mysql should use 1 or little number connection, and 1 or 
little number of select. And accept to manage numbers like many tousands as 
regular and normal value.

Got Comments ?



No Followups Have Been Posted


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1192&group_id=509




reply via email to

[Prev in Thread] Current Thread [Next in Thread]