How much sieve compute power do you have?

[pixl97]

How much processing power do you have on the sieve?


24 Hours a day
____________
1.6GHz Opteron
2.0GHz Opteron
2.0GHz Athlon XP

I just started using the night time resources of our network too.

12 Hours a day
____________
2x Athlon XP 2500+
Athlon XP 1700+
Athlon XP 2200+
Athlon XP 2100+

I assign each of them a 20G block so they finished in the 12 hour peroid, before the users come in and reboot there computers in the morning.

These are resources I may add to sieveing 12 hours a day, though it gets to be a pain to manage this many computers.

5x Athlon 1.3GHz
6x Athlon XP 1800+ or faster

If I can manage to get this up and running I should be able to total around 400G a day.

I also have 8 processors running SoB (mostly P4's)

[vjs]

If you have network access to all of them you could run task manager to autostart the program everyday at x time and stop it everyday at y time. Then monitor all of the ranges etc using sobistrator...

Make sure your allowed to run these programs we wouldn't want to see you in trouble. If the problem is the dos window there are ways around that...

I can explain.

[pixl97]

I'll have to check out the sobistrator, that looks like it would make automation much eaiser, one question, when setting up each machine in the program, will the Status file (SoBStats.dat) be different for each machine?

If there was a dos window open most users will just close it. The other issue is the business software they run is sort of crappy and will stick at 100% cpu usage, so the users are used to killing processes that run at 100% in the task manager.

[vjs]

Humm not sure about the question here but...

Yes sobstatus will be different for each machine, are you running the client over the network to a network drive?

Basically the way sobistrator works is you install sieve to each machine independantly seperate folders etc then use Sobistrator, it will tell the difference by the path names etc.

As for hiding the window there are several tools... I use a bastardized setispy configuration it autostarts and hides the window and itself, later you can close setispy and the client still runs...

Just keep the nextrange.txt full with sobistrator and monitor the progress, if you ever need to restart the client hop over to the machine and re-start it.

Hey you could always rename cmov, system maintainance, defrag, etc.

[Rychek]

Currently:

1x AthlonXP 2100+
1x A64 3400+ (2.2 Ghz 1MB L2)

Near Future:
1x AthlonXP 2500+

~6 P4s on PRP.

[engracio]

Currently:


1x Pentium 333
1x Centrino 1100
2x XP2200+
1x XP2400
2x Mobile XP3200+
5x Dual XP2400+ = 10 XP2400+
1x Dual Mobile XP3200+

~43.5 GHZ worth


e