So we've been running this annoyingly load-intensive query everyday on the BOINC database to clean up results that failed validation. It took up to an hour to run, during which it hogs a bunch of database memory and slows everything down, including workunit distribution. Why not build an index? Well, indexes still take up disk/memory, and the main table field in question is of low cardinality, and we're only hunting for a few thousand out of a millions of rows each time. So Bob was looking into implementing a new fangled mysql "trigger" to flag the few rows when they enter this bad state, making them much easier to find without needing the overkill of an index. However, we only discovered today triggers don't work in our current version of mysql. So we built an index after all. We'll see how much it helps.

Other than that and the usual database backup outage this morning, mostly spent the day moving large numbers of files/archives around to prepare to grow the workunit storage space again. I also got the new server (maul - see yesterday's note) up to speed, more or less. Still won't be live for at least a day or two, but it's working. It's a 4x2.66 GHz dual core intel with 4 GB of memory. Looks like another perfect web server to me. Also had to grow our home directory space because, as you know, no matter how much space you have, it's never enough.

Somebody pointed to an article that mentioned the Cisco 2811 has a known throughput rated at about 61 Mbps. This was a surprise to me and Jeff - I guess this wasn't what we were told, and you'd think a router with 100 Mbp ports could reach a theoretical maximum of 100 Mbps. The cap seems to be due to CPU limits, and we are doing tunnel encryption and have a small but still non-zero set of access rules. Anyway live and learn. And no further progress on that since yesterday.

Another storm is whizzing through. The top third of a 50 foot tree just broke off right outside my lab window. Cool. I understand why people are freaking out about this current weather, but this is nothing compared to the hurricanes I dealt with growing up in downstate NY.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Hey Matt,

You've been sending that weather my way. LOL I dunno if any of you folks ski, but the Sierra's got a ton of new snow. Lots of problems caused by this storm, flooding in Reno Nevada, a canal/levee broke 30 miles east of Reno in a small city called Fernley. Flooded about 2 square miles and about 400-500 homes.

Anyhow, keep up the good work.

Jeremy

---

Looks like we've hit the 60MB glass ceiling on the Cisco again.....
Lots of shorties coming thru.....
Is the multi-dataset splitting still in effect?

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Looks like we've hit the 60MB glass ceiling on the Cisco again.....
Lots of shorties coming thru.....
Is the multi-dataset splitting still in effect?

Ignored warning

Currently 6 splitters a working on the same datafile.

---

Hey Matt,

You've been sending that weather my way. LOL I dunno if any of you folks ski, but the Sierra's got a ton of new snow. Lots of problems caused by this storm, flooding in Reno Nevada, a canal/levee broke 30 miles east of Reno in a small city called Fernley. Flooded about 2 square miles and about 400-500 homes.

Anyhow, keep up the good work.

Jeremy

I heard about the broken levees there. It was on the evening news. They said some kind of rodents were to blame.

---

Looks like we've hit the 60MB glass ceiling on the Cisco again.....
Lots of shorties coming thru.....
Is the multi-dataset splitting still in effect?

I am not sure if anyone has noticed but those shorties are also coming with a very short deadline. In my modest machine they hit "running with high priority" almost right away and are cleaned up in very short time, leaving longer WUs to run after they are done.

I just got a bunch of shorts with dates around 1/17/08. They will start getting picked off in a couple of days, if they follow the pattern.

Looks like we've hit the 60MB glass ceiling on the Cisco again.....
Lots of shorties coming thru.....
Is the multi-dataset splitting still in effect?

I am not sure if anyone has noticed but those shorties are also coming with a very short deadline. In my modest machine they hit "running with high priority" almost right away and are cleaned up in very short time, leaving longer WUs to run after they are done.

I just got a bunch of shorts with dates around 1/17/08. They will start getting picked off in a couple of days, if they follow the pattern.

The short WUs have a deadline about eight-and-a-half days after issue - that's standard.

They only go into 'high priority' if you've chosen to specify a 'connect interval' (Computer is connected to the Internet about every, this website, ACCOUNT --> Computing preferences) which is a substantial proportion of those 8.5 days.

So we've been running this annoyingly load-intensive query everyday on the BOINC database to clean up results that failed validation. It took up to an hour to run, during which it hogs a bunch of database memory and slows everything down, including workunit distribution. ...

At which time (UTC) it's running every day?

---

Looks like we've hit the 60MB glass ceiling on the Cisco again.....
Lots of shorties coming thru.....
Is the multi-dataset splitting still in effect?

I am not sure if anyone has noticed but those shorties are also coming with a very short deadline. In my modest machine they hit "running with high priority" almost right away and are cleaned up in very short time, leaving longer WUs to run after they are done.

I just got a bunch of shorts with dates around 1/17/08. They will start getting picked off in a couple of days, if they follow the pattern.

The short WUs have a deadline about eight-and-a-half days after issue - that's standard.

They only go into 'high priority' if you've chosen to specify a 'connect interval' (Computer is connected to the Internet about every, this website, ACCOUNT --> Computing preferences) which is a substantial proportion of those 8.5 days.

Actually I took advantage of the information on your post. I tickled the [Computer is connected...] time to force the shorties to run with high priority. For some reason the wingmen also process the shorties fast and I get the unit credited quickly. This also has the side effect of holding the long time units for a while and increases the likelyhood that they will get credit sooner than I usually get after I send them in.

Works for me!