PvPLog 3.0.0 for WoW 2.4.2 has been released.

Enjoy,

Brad

Nice work bsmorgan

Awesome! I'll go try it out. :-)

I've got 4 no-live-PVP gamers in my Guild who actually gona take a break, and drink a beer in a local pub on jour health, bsmorgan.

I'll try this one out - it will eat data rapidly.

Thank

tuigii wrote:I've got 4 no-live-PVP gamers in my Guild ....

Ok, it didn't took long to make me understand that there is a minor flaw in the actual way of roster uploading.

One of my "18 hours a day go BG" 7/7 asked me why the uploading goes wrong every time.
A small reseach showed me that HIS pvp upload aborts with an out of memory error.
WTF, I said, I just moved my entire Guild site to a full fledged $$ server - with plenty of memory (32 Mb for apache/php uploadeable files).

This guys had a whopping 13 Mb pvplog.lua file :shock:
The upload takes time, that one thing.
But the lua parser explodes the file in a memory based array that eats up all memory.
I'm NOT gona pay me a 100 $ / month server for those PVP guys ^^

I called the next pvp player in line to check his file size. Couldn't reach him, he was in BG, of course [ confirmed : 7 Mb ]

Question : nothing can be done here, I understand, except for making the LUA parser a little bit 'intelligent' and have it breaking up these files that can be huge in smaller parts ?
If this becomes a 'real issue', then let it be a 2.0.1 WoWRoster issue
Question : instaed of flushing the entire pvplog.lua file, is there a way to say : keep the latest x thousand entries - scratch the older ones on startup ?

Let it be clear that pvplog can't handle the size of these growing lua anyway, some kind of smart-purging should be build in.

PHP sets limits on uploads and consumes a lot of memory when converting a lua file to a php array.

The parser in 2.0 is less memory intensive and is faster than in 1.7.3, but it still uses more resources than we would like it to.

The PHP array is about 5 times as large as the source file. There are potential solutions, but they need a lot of work to be implemented.

Pruning the old logs won't affect the site - existing pvplog data is not removed before loading the new.

PleegWat wrote:...
Pruning the old logs won't affect the site - existing pvplog data is not removed before loading the new.

That's good news

Have to admin that I didn't look at the roster code to see if the players pvplog details are purged before injection.

Anyway, it seems that many WoW users blow away their WTF directory anyway ones in a while (go figure why ).
A nice side effect is that it 'solves' these kind of issues.

Still, limiting the LUA file size is an WoW Addon thing. Not a WoWRoster question.

In the PvPLog too big topic, the problem with the size of the PvPLog.lua savedvariables file was discussed. In that topic I said:

I've modified the code to copy some data from PurgeLogData into PvPLogData so that old PurgeLogData can be removed with minimal adverse effect.

I've added a command (/pl keep N) that will delete old records in PurgeLogData so that only the most recent N remain.

I can look into making N a saved value and executing the "keep" command somewhere.

Brad