lolnope

I'm using magic.

 

Still magic

 

Not really, I load all my data at once and I parse it for each thing per page, but total tickets forces me to completely rewrite my code to account for all the data, not to mention it will be a lot more CPU intensive to parse it all out of the bigger logfiles.

 

The website will be down throughout the day due to updates from my host.

 

I think you misunderstood what I said, I load all lotto messages from a bunch of logfiles with each logfile being 2MB in size, I already lessened the load by a lot by making it parse every month separately, but it still takes 12 seconds to load it all.
If I were to increase the load by making it parse and process all the tickets, too, then I would increase the loadtime of that script to over 30 seconds (which is the php load limit, it will cancel the script when it reaches that point.)
I wouldn't even be able to show any of the page because the backbone of my scripts, the automatic script that updates the page every hour, would not even work.

 

I have a folder with a lot of 2mb logfiles, every hour I read through all the logfiles from the month and pull out all the lottery messages (without the ticketbuys), this is already 18k lines, then I loop through those lines to create my raw data, my interface, from there on I make each page.
When I add the lottery tickets it would literally increase the loadtime to such a degree that either php or other applications running on my server will crash.

It's a matter of integrity over functionality in this case.

 

Back online and logging!

Ew no, my own server. :b