Yes the page is very slow to load at times. It has something to do with what a previous user said about the boinc application querying the server repeatedly and causing excess load i believe.

This should get better as the boinc clients get adjusted to the new fpops estimate in the workunits.

I don't think so, if the cache is set to more days than the 12/core last, the client will request more every couple of minutes.

True, but I don't think a host which is exceeding the in progress limit triggers a DB query. The scheduler looks to see if it would even be eligible for more work, and if not gives it a come back later 'dust off'.

Of course, some of the big gun battleships are knocking off the bandits every ten minutes of so, and thus need more targets to shoot at frequently. ;-)

Alinator

I think part of the problem is with all the WUs being crunched, we're up to on average 500k WUs in the database, and 600-700k results, even with the purge being set at a day. I recompiled the purge function to allow me to set it at hours instead of days, and reduced the purge time to 6 hours. Hopefully this will help keep the database a bit smaller and things running smoothly.

---

I think part of the problem is with all the WUs being crunched, we're up to on average 500k WUs in the database, and 600-700k results, even with the purge being set at a day. I recompiled the purge function to allow me to set it at hours instead of days, and reduced the purge time to 6 hours. Hopefully this will help keep the database a bit smaller and things running smoothly.

Groan....

Well, for habitual data hounds (like me), 6 hours isn't great news...

However, that's beats insta-poof by a large margin! ;-)

In any event, if that's what it takes to keep the wheels turnin', then I'll just have to deal with it. :-)

Alinator

I think part of the problem is with all the WUs being crunched, we're up to on average 500k WUs in the database, and 600-700k results, even with the purge being set at a day. I recompiled the purge function to allow me to set it at hours instead of days, and reduced the purge time to 6 hours. Hopefully this will help keep the database a bit smaller and things running smoothly.

Groan....

Well, for habitual data hounds (like me), 6 hours isn't great news...

However, that's beats insta-poof by a large margin! ;-)

In any event, if that's what it takes to keep the wheels turnin', then I'll just have to deal with it. :-)

Alinator

I actually think we might have a little bit of a "workunit leak" from when i updated to the new assimilator+validator combo daemon. If that's the problem after i fix it we could probably increase the purge time and see how things go.

---

I actually think we might have a little bit of a "workunit leak" from when i updated to the new assimilator+validator combo daemon. If that's the problem after i fix it we could probably increase the purge time and see how things go.

Get the MOP! I got a puddle of work units over here! Rats, they are leaking all over the place ... Help ... get a bucket, get a mop, for heaven's sake get a pump ...

:)

I actually think we might have a little bit of a "workunit leak" from when i updated to the new assimilator+validator combo daemon. If that's the problem after i fix it we could probably increase the purge time and see how things go.

Get the MOP! I got a puddle of work units over here! Rats, they are leaking all over the place ... Help ... get a bucket, get a mop, for heaven's sake get a pump ...

:)

Ooooh the slow board double post. A deadly combo indeed.

---

me@rescam.org

The site's fast now :P

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

---

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

I'll still get blamed for it. Talk to 'the (in)famous guy' on your thesis team for more info.

---

me@rescam.org

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

I'll still get blamed for it. Talk to 'the (in)famous guy' on your thesis team for more info.

tsk tsk, did you crash SETI?

---

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

I'll still get blamed for it. Talk to 'the (in)famous guy' on your thesis team for more info.

tsk tsk, did you crash SETI?

Which time?

---

me@rescam.org

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

I'll still get blamed for it. Talk to 'the (in)famous guy' on your thesis team for more info.

tsk tsk, did you crash SETI?

Which time?

Oh if it happened multiple times, then we definitely can pin this one on you one way or another :D

---

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

I'll still get blamed for it. Talk to 'the (in)famous guy' on your thesis team for more info.

tsk tsk, did you crash SETI?

Which time?

XP

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

I'll still get blamed for it. Talk to 'the (in)famous guy' on your thesis team for more info.

tsk tsk, did you crash SETI?

Which time?

XP

With SP1 or SP2?

---

me@rescam.org

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

I'll still get blamed for it. Talk to 'the (in)famous guy' on your thesis team for more info.

tsk tsk, did you crash SETI?

Which time?

XP

With SP1 or SP2?

If referring to system, I was not, just :P but another type XP.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

I'll still get blamed for it. Talk to 'the (in)famous guy' on your thesis team for more info.

tsk tsk, did you crash SETI?

Which time?

XP

With SP1 or SP2?

If referring to system, I was not, just :P but another type XP.

OH. With my bigger monitor I don't have to squint.

---

me@rescam.org

Back to chug...chug...chug... again, probably due to all the systems wanting work already.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Ooooh the slow board double post. A deadly combo indeed.

I think that was the straw that broke our mysql database's back. You can now forward all your complaints to him :D

jk jk :)

I'll still get blamed for it. Talk to 'the (in)famous guy' on your thesis team for more info.

tsk tsk, did you crash SETI?

Which time?

XP

With SP1 or SP2?

If referring to system, I was not, just :P but another type XP.

OH. With my bigger monitor I don't have to squint.

LOL

Is it only me or is the site becoming sloooooow again?

---

Lovely greetings, Cori

Is it only me or is the site becoming sloooooow again?

Probably due to new users wanting the opti app and the old ones wanting their credits...

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.