InternetOfficer.com

I'm using an extra section to show a breakout of querystring variations since a lot of our site content is displayed through a single script. Right now that entails me bumping the ExtraTrackedRowsLimit to a whopping 150000, which seems like a bad idea. I tried using MaxNbOfExtra1 and MinHitExtra1 to try to truncate how much goes through, but changing them didn't seem to have any effect on how large ExtraTrackedRowsLimit needed to be.

I don't intend to have any other extra sections handle this large a request, and I really only need to see the top 50 or so. I was hoping there was a way of truncating what it had to work with in a meaningful manner. My impression from reading is that it's important to keep it at a reasonable level like the default 500.

That said, I'm making an assumption about what ExtraTrackedRowsLimit is limiting. It says that it "limits the number of possible rows an ExtraSection can report", so I assume that means it doesn't have anything to do with how many it has to sift through before reporting.

Thanks, it didn't occur to me to change the regexp. I'll have to consult with my users to find out what details they can live without, but I'm sure we can whittle it down.

Interestingly, I didn't notice a processing time increase when I added the extrasection and the 150k rows. I've been reprocessing the same 9 month batch every time I push out a change for my users to view, and it was taking about 2-3 hours consistently with DNSLookup set to 2. Setting it to 1 killed my time, though, but it warned about that in the config file. I'll be looking at replacing that with the geoip/geoipfree plugin later today.