24 hour rally

[em99010pepe]

The rally should be concentrated on the Server-Port 100 because we must clean the lower ranges. We will have plenty of time to hunt for the Top 5000 primes.
BTW, I prefer to host 3 servers rather than 4.

I've you guys seen the stats? Free-DC owns more than 70 % of the LLRnet work...

Carlos

[mdettweiler]

Originally Posted by em99010pepe

The rally should be concentrated on the Server-Port 100 because we must clean the lower ranges. We will have plenty of time to hunt for the Top 5000 primes.
BTW, I prefer to host 3 servers rather than 4.

I've you guys seen the stats? Free-DC owns more than 70 % of the LLRnet work...

Carlos

Okay, I guess that settles it then.

Yeah, I've seen the stats--hmm, us "no-team" people need to get some serious power together!

Anybody just won the lottery and got money for a farm of quad-cores?

[gd_barnes]

Originally Posted by em99010pepe

The rally should be concentrated on the Server-Port 100 because we must clean the lower ranges. We will have plenty of time to hunt for the Top 5000 primes.
BTW, I prefer to host 3 servers rather than 4.

I've you guys seen the stats? Free-DC owns more than 70 % of the LLRnet work...

Carlos

Not sure what you mean by hosting 3 vs. 4 servers. How many are you currently hosting?

I'm confused. We agreed earlier that we would do a top-5000 rally this time. I've got 6 of my work machines configured for the high-range; 4 of which are running it right now. As I recall:

First, a NPLB 320-332 rally.
Then a NPLB top-5000 rally.
Then a CRUS rally (to be determined).
Then a NPLB lower-range rally.

Or more specifically, we do several high-range rallies for each lower-range rally.

Gotta run...will be back on in 2-3 hours.


Gary

[em99010pepe]

I'm hosting 4 server, two for CRUS and two for NPLB. I prefer to host 3 because they eat a lot of memory and I only have 1GB on the server. I can tell you that the NPLB-port 100 server just eats more than 200MB of memory I suppose due to: lot's of clients connections and huge knpairs.txt. We started with a 5903 KB knpairs.txt size and now is reduced to only 5265 KB.

My position stands for the Rally on port 100 and I'll keep here my machines busy for a while.

Carlos

[mdettweiler]

Originally Posted by gd_barnes

Not sure what you mean by hosting 3 vs. 4 servers. How many are you currently hosting?

I'm confused. We agreed earlier that we would do a top-5000 rally this time. I've got 6 of my work machines configured for the high-range; 4 of which are running it right now. As I recall:

First, a NPLB 320-332 rally.
Then a NPLB top-5000 rally.
Then a CRUS rally (to be determined).
Then a NPLB lower-range rally.

Or more specifically, we do several high-range rallies for each lower-range rally.

Gotta run...will be back on in 2-3 hours.


Gary

Currently Carlos is hosting 4 servers: 2 for CRUS (Riesel and Sierpinski), and 2 for NPLB (top-5000 and lower-range). (Edit: Whoops, looks like Carlos already answered this. )

As for which rallies to do when, if I remember correctly, Carlos said that he and his Free-DC buddies estimated they could clean the lower-range server in two weeks all by themselves; thus, if we wait two more rallies until we do one on the lower-range server, it will probably be all cleaned and done by then anyway. Unless, of course, Carlos feels up to keeping the 2nd server going with the lower portion of the new 300<k<400 stuff that should be available by that time.

[mdettweiler]

Originally Posted by em99010pepe

I'm hosting 4 server, two for CRUS and two for NPLB. I prefer to host 3 because they eat a lot of memory and I only have 1GB on the server. I can tell you that the NPLB-port 100 server just eats more than 200MB of memory I suppose due to: lot's of clients connections and huge knpairs.txt. We started with a 5903 KB knpairs.txt size and now is reduced to only 5265 KB.

My position stands for the Rally on port 100 and I'll keep here my machines busy for a while.

Carlos

Hmm...well, to solve the memory problem, you could always just move one or two of the servers to another one of your machines. Then all you have to do is change the port forwarding settings in your router for the server(s) you moved, and everything will still be the same on the outside, except for a small downtime to move the server files to their new home.

[em99010pepe]

Originally Posted by Anonymous

Hmm...well, to solve the memory problem, you could always just move one or two of the servers to another one of your machines. Then all you have to do is change the port forwarding settings in your router for the server(s) you moved, and everything will still be the same on the outside, except for a small downtime to move the server files to their new home.

That's out of the question. 3 machines are at work, I can't run LLRnet server on them; 4 machines at home, the quady is a dedicated cruncher, two dual cores are not 24/7 online so that leaves me with the current server.

Carlos

[mdettweiler]

Originally Posted by em99010pepe

That's out of the question. 3 machines are at work, I can't run LLRnet server on them; 4 machines at home, the quady is a dedicated cruncher, two dual cores are not 24/7 online so that leaves me with the current server.

Carlos

Ah, I see.

One thing, though: I thought you had two quad-cores?

[em99010pepe]

Originally Posted by Anonymous

Ah, I see.

One thing, though: I thought you had two quad-cores?

I don't have but soon I'll upgrade the server to a quad-core or even a dual quad-core...lol

[mdettweiler]

Originally Posted by em99010pepe

I don't have but soon I'll upgrade the server to a quad-core or even a dual quad-core...lol

Ah, I see. I don't know where I got the idea that you had two!

[gd_barnes]

Originally Posted by em99010pepe

I'm hosting 4 server, two for CRUS and two for NPLB. I prefer to host 3 because they eat a lot of memory and I only have 1GB on the server. I can tell you that the NPLB-port 100 server just eats more than 200MB of memory I suppose due to: lot's of clients connections and huge knpairs.txt. We started with a 5903 KB knpairs.txt size and now is reduced to only 5265 KB.

My position stands for the Rally on port 100 and I'll keep here my machines busy for a while.

Carlos

I thought for a long time while I had my kids over tonight before logging back on late here. I've done an "about face". You know it's been you that have brought all the Free-DC people here and you're running the servers on your machines. Also, having as much power as a rally will bring to a range that is not top-5000 is hard to come by. All you have to do is look at k>1000 to realize that a large majority of people are only interested in top-5000 primes instead of accurate and complete lists of primes. Even if we don't have massive firepower, we can probably get at least a reasonable number of people to search top-5000 ranges. What is not easy is getting people to search the lower ranges.

As long as we're moving forward toward the goals established by the project, having the rally on the lower range works for me. Filling in this range is a big step in that direction. I feel that the original #1 priority is now in good shape. That is I think we're past the 'danger zone' of having any primes n>333.3K not being top-5000 in a few months since we've already searched most k/n pairs up to ~n=360K.

The next most important step will be getting 300<k<400 searched quickly up to n=350K-360K. This k-range will have more of a 'double-check' flavor to it with probably about 20-25% of primes already found but becoming less as the n-range gets higher. That is why I initially avoided sieving it. I think having a double-check flavor to it makes it good for a rally. Some people won't like double-checking as much but are happy to participate in a fun rally with still a good chance of finding new top-5000 primes.

So...let's do the lower range for this rally. Then I'd like to do the next rally on 300<k<400 for n>333.3K 2-3 weeks after that if everyone can continue the break-neck pace. Sieving to P=6T will be complete Feb. 28th-29th. That will still allow over a week to get the new range loaded into the server, port # changed, and all that stuff.

Then in 5-6 weeks, I'd like to do a rally at CRUS. After that, we can decide where to go from there. FYI for those who don't know: CRUS = the "Conjectures 'R Us" project.

Thoughts, opinions, objections anyone?


Gary