a ? about distibuting WU's

Marrkks

Senior member
Jun 9, 2001
309
0
0
I currently have 2 xp1600's and a k63 crunching and I'm running seti queue3.03.2.2a. is there any way to give my k63 only vhar wu's? I can't find any way to do this. is there another "Q" that will do this? my poor lil k6 takes a pretty big hit in procssing times when it gets a vlar wu--hours difference. I thought I read some posts in here awhile ago that referred to something like this.

btw-I also have 1 or 2 assims on the horizon that this might also apply to. (cely 800 and k6-400)
 

blade47

Golden Member
Dec 12, 1999
1,353
0
0
I'm sure you could do it manually somehow, though it would be a bit of a pain.

If you have a linux machine connecting to your Q you can turn on setiQ's vlar routing and it will send most of the vlar wu's to the non-windows que. I have both windows and a linux machine connecting to my Q and there are 2 seperate ques for the different OS's. With Vlar routing on when setiQ downloads a vlar wu it will try and put it in the linux client's Q. Since the linux client doesn't suffer the performance hit it really helps out alot.

I still have a C-300a @ 450mhz on my network and it does wu's in around 12 hrs on avg but the vlar's take around 18hrs!!!! With vlar routing on almost every wu with vlar is sent to my linux gateway which is an old P2-233 @ 300mhz and it does them consistently at around 18 hrs no matter what the range. Which allows the windows based machines to do alot more wu's since they don't get bogged down.

I think everyone should have at least 1 linux machine connecting to their Q just to handle the vlar wu's. I'm sure someone has some suggestions for an all windows network though. :D
 

Assimilator1

Elite Member
Nov 4, 1999
24,165
524
126
Another way around it (if practicle) would be to install Win2k on the K6-3 machine ,this would also suffer farless than the Win9x/ME OS's
 

Baldy18

Diamond Member
Oct 30, 2000
5,038
0
0
The method described by blade_47 will also work with Windows NT/2K/XP. VLAR routing will keep VLARs away from Windows 95/98/ME clients. I don't know of a way though to make it or any other program send all VHARs to a specific client.

So I wouldn't put Windows 2K on the K6-3. I toulf put it on one of the other machines and turn VLAR routing on.
 

Marrkks

Senior member
Jun 9, 2001
309
0
0
thanks for the replies.

first of all I couldn't even find the option for "vlar routing". I did find it tonight-under the Reports header, I thought it would be under the settings.:confused: and I see that the only option is to "avoid win-cmdline". since I won't have Winxp(or *nix) for at least another month I'll just keep letting the wu's fall were they may.:p:)
 

JWMiddleton

Diamond Member
Aug 10, 2000
5,686
172
106
Originally posted by: blade_47
Cool I didn't know it routed differently for NT and XP. :D

Yep, by adding a couple of Athlon XPs running XP I helped my daily average a good bit. I never have to worry about Win9x clients getting VLAR WUs! Gotta love it!!

 

blade47

Golden Member
Dec 12, 1999
1,353
0
0
Hehe I bet it did JW. :)

Just adding my linux gateway helped my production out though it's so slow I still get a few vlar's in winME sometimes. :(

I am planning on adding another Linux node to my network in the next few weeks though so maybe that'll help me out some more. :D