unforum

[arnezami]

[chimera245]

In actual fact I am planning on flexible length data grabs (i.e. range) - for throttling at the server end purposes.

I should probably elucidate further.

2.0 of the Labour13 client will (if all goes well) feature a -f option to use the Fast Client code from Sk1zz. This however will only operate on certain platforms, while the rest of the code remains for the others. This alone necessitates a flexibility in work unit assignment. I also want to (from a server standpoint) be able to vary the number of work units assigned to the clients based upon server load and other factors.

The idea therefore is that the client will request work unit(s), and will get an appropriate amount - for a non -f client this will be a limited number (it may be more than one though if server congestion is an issue), for the -f client it will be a larger number.

Once the client can cater for more than one work unit - it can essentially cater for any number (within reason) if I do it right.

[Guin]

The prize pool continues to grow. I have acquired a spare (and original) card wallet to place all the shiny new and unscratched cards into - nice for a starter or even old hand - an almost (we have every wave 1 and 2 card excluding one purple (#175 Binary) some blacks (#206, #215, #217, #219) and most silvers (although we have polar #247 and 13th #251) complete set of cards). I have been offered all wave 3 purples and am just awaiting the MC contribution before I post a new picture for all to drool over.

So PLEASE keep them clients running. even if you can only contribute an hour a day however small your contribution it will make the task seem easier and reduce the workload helping us solve this card once and for all.

If you need the client a new version is available at 13th labour and the Live Journal is also available to check progress, news, and our little running puzzles and competitions set to while away the hours while we process these work units and offer a little R&R from any of those pesky silvers.

[jazzychad]

8 byte key

[arnezami]

[hexDa3m0n]

Re: 8 byte key

[Guin]

Re: 8 byte key

[Fuseunderground]

Re: 8 byte key

[Skizz]

arnezami:
Now there's a thought - it shouldn't be too difficult to remove the SSE stuff, and I can do it automatically too - there's a bit in the CPUID result that is set if SSE2 is present.
I'm currently working with chimera245 on V2 of the client so I'll definitely look into that.

Oh, and about the whole key thing - the client at the moment will only do keys "xxxxyyyy" where the X's are provided by the server and Y's are iterated by the client. At the moment the client (and server) only iterates 0-9,A-Z,A-Z (the fast client also does ':'). Expanding the key space search will require modifying the client and the server - doing a full 4 character key search (ascii 0 to ascii 255 for each y) using the fast client on a fast CPU will take an hour, so it will be a major undertaking. If this first go doesn't produce a result, I'd be tempted to do a search in the range ascii 32 to ascii 127 as the next step.

Skizz

[chimera245]

Just an update, I'm working with Sk1zz on getting the processor specific optimizations in, but there is a version of the general use client (1_1_0) in beta now which bring the processing time down by a factor of 4 -5 - I have it doing work units in 2 mins now .

This should be available early next week.

[kniteli]

any hope of a multi threaded one for dual cores? i know im running at 50% because of it, could be running alot faster than i am atm.

[Fuseunderground]

[kniteli]

oo thank you, im dumb (or just tired lol), actually see my proc peaked at 100 for the first time since i got it.

[Flynn]

[Fuseunderground]