Tweet
Reporting for duty, sir!
First, let's recap why I'm indeed reluctant to use "live" (cgi) data for seti.matroxusers, and use their "static" data instead:
- Seti is obviously having a hard time coping with the database-load. Just read the Technical news reports. Just about every one of them is about database performance. Querying another 200 times/day isn't going to improve that.
- I'm running this thing from a *very* fast network-connection, yet every tenth (or so, rough estimate) connection to Seti's stats-page fails for unknown reasons. So even their network-connections seem to be heavily loaded at times. Again, retrieving another 200 cgi stats-pages/day isn't going to help.
- Seti is putting a lot of effort in keeping the "daily" stats up-to-date, and things have improved lately.
In summary: I'd rather leave it to Seti to improve the quality and frequency of the stats. I'd hate to make the problem worse by pounding them with extra queries.
That being said... I guess some extra queries for our "window of interest" isn't going to hurt all that much.
Some thoughts: why don't you use Excel (instead of SetiTeam) to grab the stats: Data, External Data, and then Create/Save/Use a web query for every team in the current window of interest. Create some extra worksheets for the table and for the histories. That way, you could automate the process of grabbing the data, generating the table and storing the summaries. That should be doable.
(Few hours later...)
In fact, I cooked up a lil' something in Excel just now. It's a little rough around the edges (well, more than a little, actually
...), but it will fetch and store data and produce a rudimentary table for the data you want. Drop me an e-mail if you want to play around with it.
Martin
First, let's recap why I'm indeed reluctant to use "live" (cgi) data for seti.matroxusers, and use their "static" data instead:
- Seti is obviously having a hard time coping with the database-load. Just read the Technical news reports. Just about every one of them is about database performance. Querying another 200 times/day isn't going to improve that.
- I'm running this thing from a *very* fast network-connection, yet every tenth (or so, rough estimate) connection to Seti's stats-page fails for unknown reasons. So even their network-connections seem to be heavily loaded at times. Again, retrieving another 200 cgi stats-pages/day isn't going to help.
- Seti is putting a lot of effort in keeping the "daily" stats up-to-date, and things have improved lately.
In summary: I'd rather leave it to Seti to improve the quality and frequency of the stats. I'd hate to make the problem worse by pounding them with extra queries.
That being said... I guess some extra queries for our "window of interest" isn't going to hurt all that much.
Some thoughts: why don't you use Excel (instead of SetiTeam) to grab the stats: Data, External Data, and then Create/Save/Use a web query for every team in the current window of interest. Create some extra worksheets for the table and for the histories. That way, you could automate the process of grabbing the data, generating the table and storing the summaries. That should be doable.
(Few hours later...)
In fact, I cooked up a lil' something in Excel just now. It's a little rough around the edges (well, more than a little, actually
...), but it will fetch and store data and produce a rudimentary table for the data you want. Drop me an e-mail if you want to play around with it.Martin
Comment