MJ12 starting to outgrow the client

:D alexc
I'm having trouble logging into the MJ12 forum atm, hence my post here.

I thought about posting this as a bug in the MJ12 project forum, but it isn't a problem, much more an indicator of success:

The MJ12 project is now so successful that the number of URLs confirmed has reached 11 digits.

In the client ver 1.2.7, on the Status tab, in the Distributed Network box, in the Crawling segment, the 1st digit of the number of URLs crawled has cascaded down one line!

The number is so big it's out-growing the original design of the client.

w00t! :cool:
Well done Majestic-12.

(I'll look out for the layout-mod in the next Major Release)

hehe, I know, pretty amazing numbers! :shock:

I added enougn space for 999,999,999,999 urls in v1.2.8 beta 3, available here: http://www.majestic12.co.uk/forum/viewtopic.php?t=1745 :cool:

Well done all, it just shows what distributed computing can achieve, just imagine if 100,000 people joined the project :shock:

AMDave

Thank you for posting about MJ-12. I had forgotten it and now when we have a break from the race I think to run this project.

Lagu :)

Yes, thanks for reminding us. I tried to run it. It downloads the buckets fine. Archives them fine. Uploads them wrong...

I think it is my ISP, again... They like to block traffic. The node says i have uploaded 13 buckets today but there has been no upload traffic. MY ISP does the same thing in almost all P2P apps. It will let me download, but no upload. They must think MJ-12 is a P2P proggy. :lol:

Does anyone else have Cox High Speed Internet?

Quote:

---

Originally Posted by AMD-USR_JL

The node says i have uploaded 13 buckets today but there has been no upload traffic.

---

What makes you think there was no upload traffic? There is safety checksumming in uploads so that if someone interferes then it should be detected. What you may want to try to do is this: go to Options->Connection and unchedk "use direct connections", some ISPs use transparent proxies that interfere with uploads, but with that option unchecked it should work.

thanks a lot, i will try. :D

Alexc

Thank you. I knew you should have a solution in your hand.

Lagu :D

Hopefully it will work - it should reall, otherwise something is very wrong if node supports uploads are done but you dont see that in stats!

It did! Thanks so much MJ-12. :D

You welcome! I am going to build in line checker into node to detect if there are transparent proxies that cause issues and automatically fallback to somewhat slower but more reliable HTTP connectivity.

alexc,

I am finding ver 1.2.8.b.3.1 to very stable and the restarts have stopped happening. Well done.

Excellent news! You may want to try external process archiving (don't confuse with external RAR archiver which can also be used) that seems to save memory, see checkbox in Options->Archiving. :)

Yes. I read the notes in the project forum.
I was not aware of those problems.
I had not experienced them.

I am using the external option and it is working fine.
I do not see any memory issues.
But I did not see any before either.

PLEASE download the latest beta on this link: http://majestic12.co.uk/files/mj12no...n32_v128b4.zip

The other betas have some serious problems with external archiver which will cause the node to get stuck in a loop.

I have confirmed that this new beta is working correct at this point in time.

now happilly running 1.2.8.b.4.3
Thx.