Announcement

Collapse
No announcement yet.

Long waiting times for posting

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • naszeaudio
    replied
    Originally posted by Mark.B View Post

    At the moment run them whenever the site appears to slow down. Once a week should be ok unless you have masses of traffic, but more often will not hurt if you can be bothered. You can do it in the admincp if you give yourself query running permissions in the core config file.

    The issue itself should be fixed in 5.3.4 - first public alpha of which, by coincidence, has just been released.
    Will do, thanks.

    Well, it is very fast now.
    It was very frustrating for lots of people on my forum...After 18 months DB was 3.1GB, and now went down to 771MB after your suggested comments. Shocking.

    I decided to skip 5.3.3, good to hear 5.3.4 will have this implemented.


    Leave a comment:


  • Mark.B
    replied
    Originally posted by naszeaudio View Post

    It works much faster for me. I will wait for my '2minutes' user feedback but I think this was the problem. Click image for larger version Name:	hi.gif Views:	1 Size:	2.8 KB ID:	4379203

    I was doing optimization and repair, but I did not know I have to delete cache, cacheevent and searchlog.
    How often should I repet those commends?
    Should I run other maintenance commends on DB as well?
    At the moment run them whenever the site appears to slow down. Once a week should be ok unless you have masses of traffic, but more often will not hurt if you can be bothered. You can do it in the admincp if you give yourself query running permissions in the core config file.

    The issue itself should be fixed in 5.3.4 - first public alpha of which, by coincidence, has just been released.

    Leave a comment:


  • naszeaudio
    replied
    Originally posted by Mark.B View Post
    Yes if you have a table prefix you will need to add that into the queries.
    It works much faster for me. I will wait for my '2minutes' user feedback but I think this was the problem. Click image for larger version  Name:	hi.gif Views:	1 Size:	2.8 KB ID:	4379203

    I was doing optimization and repair, but I did not know I have to delete cache, cacheevent and searchlog.
    How often should I repet those commends?
    Should I run other maintenance commends on DB as well?

    Leave a comment:


  • Mark.B
    replied
    Yes if you have a table prefix you will need to add that into the queries.

    Leave a comment:


  • naszeaudio
    commented on 's reply
    Ok, my tables name is vb_cache. Will test it. Thank you again.

  • naszeaudio
    replied
    Originally posted by Mark.B View Post
    Please run these three queries on the database.

    Code:
    DELETE FROM cache
    DELETE FROM cacheevent
    DELETE FROM searchlog
    Thank you Mark.
    Is this all I have to write there?
    I get popup like this:
    Click image for larger version

Name:	Capture.JPG
Views:	22
Size:	234.8 KB
ID:	4379195

    Leave a comment:


  • Mark.B
    replied
    Please run these three queries on the database.

    Code:
    DELETE FROM cache
    DELETE FROM cacheevent 
    DELETE FROM searchlog

    Leave a comment:


  • naszeaudio
    started a topic Long waiting times for posting

    Long waiting times for posting

    We have this problem since quite a while.
    It appears that users with older accounts, 5000+ posts, 500+ photos, have long waiting time when they writing posts. Even up to 2 minuts.
    We made a test, and I created for this user new account, and he was able to write in 2 seconds ('Waiting..' at the top was gone in 2 seconds).
    Any idea why this happens?

    We use vbulletin 5.3.2 patch level 1

Related Topics

Collapse

Working...
X