#33 Poor performance on SystemInfo macro (thus, RecentChanges)

closed-later
nobody
None
5
2003-05-02
2003-05-01
No

We've been using our wiki for about a year and a half.
The event log has obviously gotten quite large (~24MB).

As a result, the RecentChanges page has gotten slower
and slower. After looking into the SystemInfo macro
(used at the top of the RecentChanges page), I saw that
the entire event log file is read line-by-line (and
each line is fully parsed! ugh) simply so that the
SystemInfo macro can report the number of entries.

Can you make this more efficient/practical? ie.. add a
numEvents( ) method to eventlog.py that more
efficiently provides this info.

Thanks.

Discussion

  • Jürgen Hermann

    Jürgen Hermann - 2003-05-02
    • status: open --> closed-later
     
  • Jürgen Hermann

    Jürgen Hermann - 2003-05-02

    Logged In: YES
    user_id=39128

    You have to rotate or delete the event.log on a regular
    basis. There'll be no immediate resolution.

    RC is influenced by editlog, not event.log. If you have many
    edits, that has to be rotated, too (don't delete it).

     
  • Jürgen Hermann

    Jürgen Hermann - 2003-05-02

    Logged In: YES
    user_id=39128

    Do you have the SystemInfo macro still remaining on the RC
    page?! Remove it, it's long gone from the master RC page
    for this exact reason.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks