Somebody should file a patent for a BIOS setting to restart the computer after a loss of power, but with a random delay of 0...[configurable] setting :-). Oh no you can't, it's prior art:-), at least now.
Well another night has passed and its time to crawl under the covers and hope my work gets sent before I get up later this afternoon. Somehow I don't think things will wait until Friday. But that's the fun part.
Somebody should file a patent for a BIOS setting to restart the computer after a loss of power, but with a random delay of 0...[configurable] setting :-). Oh no you can't, it's prior art:-), at least now.
I just queued up a bunch (24 to be exact). Hopefully that'll get this machine through the outage.
Well, 24 tasks could be a whole heap or not much at all depending on how fast/no. of cores your machine has :-). You need to talk in "days of cache" that you have stored away. Before my little power outage, about a third of my machines had 7 or more days of work stored up. About another third had about 3-5 days and the rest were due to get their fill this morning.
I should have figured on Murphy's Law and finished the job yesterday.
Now that all the machines are going strong again, the scheduler doesn't look to be too cooperative at the moment. It's now 9.00PM here in OZ and I'm just deciding whether or not to head home or see if I can get some of the hosts "topped-up" that need a top up. Now basically everything is "condition red" on the bridge again so things aren't looking too hopeful.
EDIT: "Cap'n, I've managed to squeeze a bit more juice out of the warp core and it's just that pesky scheduler that's still not cooperating. I've just got a few more tricks to try and hopefully she'll be fully green again soon. Either that or she may even blow completely .... " :-).
... but with a random delay of 0...[configurable] setting :-). Oh no you can't, it's prior art:-), at least now.
One small problem to solve would be how to get the BIOS to decide the particular value of the random delay quickly enough :-). After all, with the circuit breaker already tripped and power disappearing rather fast, I do think the BIOS will always be too slow on the uptake to get the random value figured out in time. I can almost hear the BIOS screaming in frustration, "If you'd only given me another 10 nanosecs, I could have decided on the delay and you wouldn't have had to pull the plug on me yet again!!" :-).
(I'm a bit dense so I'm not quite sure what you meant by the "it's prior art" comment but perhaps it was something along the lines of my comment above?)
(I'm a bit dense so I'm not quite sure what you meant by the "it's prior art" comment but perhaps it was something along the lines of my comment above?)
Now that he's mentioned it publicly, without a patent, it becomes 'prior art' ie. now currently known so it can't be patented from here onwards as a 'new' idea ..... :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
if( mains voltage is rising from 0 to nominal && power switch is in ON position) {
delay = random(0,max_delay);
wait(delay)
power system up.
}
"Prior art" just means that you can't patent something that was already described or even in use by someone else before you filed for that patent :-), even if that other person did NOT file a patent. It's got to be new.
Now that he's mentioned it publicly, without a patent, it becomes 'prior art' ...
I told you I was a bit dense :-).
I was wondering if he was somehow being really tricky and testing out how many people would swallow the notion that a BIOS delay could stop the power surge and hence stop tripping the breakers :-).
I didn't recognise the full "prior art" term because I was too focussed on just the word "prior" as in which event is "prior" to which :-).
We've started to 'drain' the S5R3b Workunit generator (WUG), i.e. told it to generate all remaining S5R3 Workunits and put them into the database. We hope that this will shift a bit of load from the main server to the database server. In a few hours you'll notice that the WUG doesn't run anymore, which is nothing to worry about.
Also we nudged some S5R2 and S5R3a workunits that got stuck, so we can hope to have these runs finished before Friday.
Somebody should file a patent
)
Somebody should file a patent for a BIOS setting to restart the computer after a loss of power, but with a random delay of 0...[configurable] setting :-). Oh no you can't, it's prior art:-), at least now.
CU
Bikeman
Well another night has passed
)
Well another night has passed and its time to crawl under the covers and hope my work gets sent before I get up later this afternoon. Somehow I don't think things will wait until Friday. But that's the fun part.
RE: Several hours ago, ...
)
ROFL! They've probably all joined the Borg ..... :-)
Cheers, Mike.
( edit ) Any gossip on the new server box specs Bernd?
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: Somebody should file a
)
That's funny! [edit/: & also a great idea. -edit]
Regards.
RE: I just queued up a
)
Well, 24 tasks could be a whole heap or not much at all depending on how fast/no. of cores your machine has :-). You need to talk in "days of cache" that you have stored away. Before my little power outage, about a third of my machines had 7 or more days of work stored up. About another third had about 3-5 days and the rest were due to get their fill this morning.
I should have figured on Murphy's Law and finished the job yesterday.
Now that all the machines are going strong again, the scheduler doesn't look to be too cooperative at the moment. It's now 9.00PM here in OZ and I'm just deciding whether or not to head home or see if I can get some of the hosts "topped-up" that need a top up. Now basically everything is "condition red" on the bridge again so things aren't looking too hopeful.
EDIT: "Cap'n, I've managed to squeeze a bit more juice out of the warp core and it's just that pesky scheduler that's still not cooperating. I've just got a few more tricks to try and hopefully she'll be fully green again soon. Either that or she may even blow completely .... " :-).
Cheers,
Gary.
RE: ... but with a random
)
One small problem to solve would be how to get the BIOS to decide the particular value of the random delay quickly enough :-). After all, with the circuit breaker already tripped and power disappearing rather fast, I do think the BIOS will always be too slow on the uptake to get the random value figured out in time. I can almost hear the BIOS screaming in frustration, "If you'd only given me another 10 nanosecs, I could have decided on the delay and you wouldn't have had to pull the plug on me yet again!!" :-).
(I'm a bit dense so I'm not quite sure what you meant by the "it's prior art" comment but perhaps it was something along the lines of my comment above?)
Cheers,
Gary.
RE: (I'm a bit dense so I'm
)
Now that he's mentioned it publicly, without a patent, it becomes 'prior art' ie. now currently known so it can't be patented from here onwards as a 'new' idea ..... :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
What I was thinking
)
What I was thinking about:
if( mains voltage is rising from 0 to nominal && power switch is in ON position) {
delay = random(0,max_delay);
wait(delay)
power system up.
}
"Prior art" just means that you can't patent something that was already described or even in use by someone else before you filed for that patent :-), even if that other person did NOT file a patent. It's got to be new.
CU
Bikeman
RE: Now that he's mentioned
)
I told you I was a bit dense :-).
I was wondering if he was somehow being really tricky and testing out how many people would swallow the notion that a BIOS delay could stop the power surge and hence stop tripping the breakers :-).
I didn't recognise the full "prior art" term because I was too focussed on just the word "prior" as in which event is "prior" to which :-).
Cheers,
Gary.
We've started to 'drain' the
)
We've started to 'drain' the S5R3b Workunit generator (WUG), i.e. told it to generate all remaining S5R3 Workunits and put them into the database. We hope that this will shift a bit of load from the main server to the database server. In a few hours you'll notice that the WUG doesn't run anymore, which is nothing to worry about.
Also we nudged some S5R2 and S5R3a workunits that got stuck, so we can hope to have these runs finished before Friday.
BM
BM