Results 1 to 3 of 3

Thread: GetMiniCalRequest Slowness

  1. #1
    marinew is offline Senior Member
    Join Date
    Aug 2007
    Location
    France - Bretagne
    Posts
    55
    Rep Power
    8

    Default GetMiniCalRequest Slowness

    Hello,

    In calendar view, when I'm paginating through weeks, after a time, it becomes very slow.
    After analyzing requests with Firebug "Network" tab, I see that it's "GetMiniCalRequest" requests that are very long (about 10 seconds), whereas "SearchRequest" is quite fast.

    What can this be due ?
    How can I see what's happening during these 10 seconds ?

    Thanks for any help !
    Marine

    Zimbra version : Release 5.0.4_GA_2101.DEBIAN4.0 DEBIAN4.0 FOSS edition

  2. #2
    marinew is offline Senior Member
    Join Date
    Aug 2007
    Location
    France - Bretagne
    Posts
    55
    Rep Power
    8

    Default

    We noticed that navigating through weeks on large calendars is slower than on smaller calendars, which is logical.
    But I was wondering : we have a very large amount of appointments in these calendars, as zimbra is used to manage schedule of a medical officine (up to 50 or 60 appointments per day and per doctor for some days of the week).
    Is Zimbra sized to manage this type of volumetry over time ?

    Here are calendars that are simultaneously displayed for a user, with the number of items for each.

    Id View Unread Msg Count Path
    ---------- ---- ---------- ---------- ----------
    1 conv 0 0 /
    16 docu 0 0 /Briefcase
    10 appo 0 12 /Calendar
    264 appo 0 834 /Calendar/_Absences
    261 appo 0 466 /Calendar/_Astreintes
    262 appo 0 982 /Calendar/_Autres_activites
    263 appo 0 0 /Calendar/_Prive
    257 appo 0 941 /Calendar/_Planning_CS
    258 appo 0 753 /Calendar/_Planning_OP
    259 appo 0 19125 /Calendar/_RDV_CS
    260 appo 0 2781 /Calendar/_RDV_OP


    Thanks for your opinion.
    Marine

    PS : I know we use a very old version of Zimbra, but it has well worked for years, and I really need help to get back to previous situation. Thanks !

  3. #3
    marinew is offline Senior Member
    Join Date
    Aug 2007
    Location
    France - Bretagne
    Posts
    55
    Rep Power
    8

    Default

    I activated logs :

    zimbra@serveur:~/log$ zmprov getAccountLoggers <myAccount>
    zimbra.dbconn=debug
    zimbra.webclient=debug
    zimbra.sqltrace=debug
    zimbra.perf=debug
    zimbra.soap=debug
    zimbra.calendar=debug

    Then I clicked on week change button in web client, and I looked at logs in /opt/zimbra/log/mailbox.log (see at the end of the post).
    If I interpret this correctly, it seems the time is lost in a MySql "commit" (about 5 seconds), but I don't understand :
    - Why there is a "commit" after a "select" command...
    - Why this commit is so long

    Or maybe it's not the commit that is long, but something between this commit and the following request ?? How to check this ?


    Mailbox.log :
    2012-06-15 23:03:22,833 DEBUG [btpool0-242083] [name=my_user@my_domain.fr;ip=127.0.0.1;ua=ZimbraWe bClient - FF3.0 (Linux)/5.0.4_GA_2101.DEBIAN4.0;] soap - SOAP request:
    {
    "Body": {
    "GetMiniCalRequest": {
    (...)
    2012-06-15 23:03:23,157 DEBUG [btpool0-242024] [name=my_user_p@my_domain.fr;aname=my_user@my_domai n.fr;mid=24;ip=my_ip;ua=zclient/5.0.4_GA_2101.DEBIAN4.0;] sqltrace - SELECT mi.id, mi.type, mi.parent_id, mi.folder_id, mi.index_id, mi.imap_id, mi.date, mi.size, mi.volume_id, mi.blob_digest, mi.unread, mi.flags, mi.tags, mi.subject, mi.name, mi.metadata, mi.mod_metadata, mi.change_date, mi.mod_content FROM mboxgroup24.appointment AS ci, mboxgroup24.mail_item AS mi WHERE ci.start_time < 2011-12-12 00:00:00.0 AND ci.end_time > 2011-10-31 00:00:00.0 AND mi.id = ci.item_id AND mi.type IN (11) AND ci.mailbox_id = 24 AND mi.mailbox_id = ci.mailbox_id AND folder_id = 257 - 8ms, conn=20225905
    2012-06-15 23:03:23,159 DEBUG [btpool0-242024] [name=my_user_p@my_domain.fr;aname=my_user@my_domai n.fr;mid=24;ip=my_ip;ua=zclient/5.0.4_GA_2101.DEBIAN4.0;] sqltrace - commit, conn=20225905
    2012-06-15 23:03:23,180 DEBUG [btpool0-242024] [name=my_user_p@my_domain.fr;aname=my_user@my_domai n.fr;mid=24;ip=my_ip;ua=zclient/5.0.4_GA_2101.DEBIAN4.0;] sqltrace - SELECT mi.id, mi.type, mi.parent_id, mi.folder_id, mi.index_id, mi.imap_id, mi.date, mi.size, mi.volume_id, mi.blob_digest, mi.unread, mi.flags, mi.tags, mi.subject, mi.name, mi.metadata, mi.mod_metadata, mi.change_date, mi.mod_content FROM mboxgroup24.appointment AS ci, mboxgroup24.mail_item AS mi WHERE ci.start_time < 2011-12-12 00:00:00.0 AND ci.end_time > 2011-10-31 00:00:00.0 AND mi.id = ci.item_id AND mi.type IN (11) AND ci.mailbox_id = 24 AND mi.mailbox_id = ci.mailbox_id AND folder_id = 258 - 7ms, conn=20225905
    2012-06-15 23:03:23,182 DEBUG [btpool0-242024] [name=my_user_p@my_domain.fr;aname=my_user@my_domai n.fr;mid=24;ip=my_ip;ua=zclient/5.0.4_GA_2101.DEBIAN4.0;] sqltrace - commit, conn=20225905
    2012-06-15 23:03:23,218 DEBUG [btpool0-242024] [name=my_user_p@my_domain.fr;aname=my_user@my_domai n.fr;mid=24;ip=my_ip;ua=zclient/5.0.4_GA_2101.DEBIAN4.0;] sqltrace - SELECT mi.id, mi.type, mi.parent_id, mi.folder_id, mi.index_id, mi.imap_id, mi.date, mi.size, mi.volume_id, mi.blob_digest, mi.unread, mi.flags, mi.tags, mi.subject, mi.name, mi.metadata, mi.mod_metadata, mi.change_date, mi.mod_content FROM mboxgroup24.appointment AS ci, mboxgroup24.mail_item AS mi WHERE ci.start_time < 2011-12-12 00:00:00.0 AND ci.end_time > 2011-10-31 00:00:00.0 AND mi.id = ci.item_id AND mi.type IN (11) AND ci.mailbox_id = 24 AND mi.mailbox_id = ci.mailbox_id AND folder_id = 259 - 24ms, conn=20225905
    2012-06-15 23:03:23,263 DEBUG [btpool0-242024] [name=my_user_p@my_domain.fr;aname=my_user@my_domai n.fr;mid=24;ip=my_ip;ua=zclient/5.0.4_GA_2101.DEBIAN4.0;] sqltrace - commit, conn=20225905
    2012-06-15 23:03:28,481 DEBUG [btpool0-242024] [name=my_user_p@my_domain.fr;aname=my_user@my_domai n.fr;mid=24;ip=my_ip;ua=zclient/5.0.4_GA_2101.DEBIAN4.0;] sqltrace - SELECT mi.id, mi.type, mi.parent_id, mi.folder_id, mi.index_id, mi.imap_id, mi.date, mi.size, mi.volume_id, mi.blob_digest, mi.unread, mi.flags, mi.tags, mi.subject, mi.name, mi.metadata, mi.mod_metadata, mi.change_date, mi.mod_content FROM mboxgroup24.appointment AS ci, mboxgroup24.mail_item AS mi WHERE ci.start_time < 2011-12-12 00:00:00.0 AND ci.end_time > 2011-10-31 00:00:00.0 AND mi.id = ci.item_id AND mi.type IN (11) AND ci.mailbox_id = 24 AND mi.mailbox_id = ci.mailbox_id AND folder_id = 260 - 23ms, conn=20225905
    2012-06-15 23:03:28,490 DEBUG [btpool0-242024] [name=my_user_p@my_domain.fr;aname=my_user@my_domai n.fr;mid=24;ip=my_ip;ua=zclient/5.0.4_GA_2101.DEBIAN4.0;] sqltrace - commit, conn=20225905
    2012-06-15 23:03:28,534 DEBUG [btpool0-242024] [name=my_user_p@my_domain.fr;aname=my_user@my_domai n.fr;mid=24;ip=my_ip;ua=zclient/5.0.4_GA_2101.DEBIAN4.0;] soap - SOAP response:
    {
    "Body": {
    "GetMiniCalResponse": {
    (...)

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Increadable slowness on the UI
    By Meowmixjinx in forum Administrators
    Replies: 0
    Last Post: 09-02-2008, 08:47 AM
  2. 4.5.6 -> 5.0.8 slowness problems
    By Meowmixjinx in forum Administrators
    Replies: 1
    Last Post: 08-08-2008, 12:36 PM
  3. slowness of GAL
    By neverland in forum Zimbra in Education
    Replies: 0
    Last Post: 05-13-2008, 12:31 AM
  4. GetMiniCalRequest Method Error
    By LMStone in forum Administrators
    Replies: 8
    Last Post: 04-10-2008, 06:44 PM
  5. Client Slowness in demo
    By flake in forum Users
    Replies: 8
    Last Post: 10-31-2005, 03:09 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •