Pages:
Author

Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 12. (Read 379084 times)

legendary
Activity: 1750
Merit: 1007
US West has been taken offline.  The website will also be relocating this weekend.  The new EU (DE) cluster has been expanded more as well to keep everything running smoothly.

For those connecting with direct IP or like me, have to create a custom route, use IP: 78.46.184.206

For the time being, I would recommend anybody that -must- connect by a specific IP to use: 78.46.186.26.  I will put up another server later on that is specifically for people with special circumstances.
member
Activity: 109
Merit: 10
US West has been taken offline.  The website will also be relocating this weekend.  The new EU (DE) cluster has been expanded more as well to keep everything running smoothly.

For those connecting with direct IP or like me, have to create a custom route, use IP: 78.46.184.206
newbie
Activity: 11
Merit: 0
Smiley Smiley Smiley Grin Grin Grin

Happy that I found TWO blocks for the pool today!!!

 Smiley Donations welcomed: 19QkGqwfarhdWXqW9SiH3ZzNfjNWLTJHkV
newbie
Activity: 11
Merit: 0
 Smiley Smiley Smiley Grin Grin Grin

Happy that I found TWO blocks for the pool today!!!
sr. member
Activity: 383
Merit: 250
UTC time adjustments on website... Please?
legendary
Activity: 1750
Merit: 1007
The current round of 5+ hours is normal then? Once it gets that long I start to worry something is screwy
even though I realize a 10 million share round ain't impossible.

The rounded ended close to an hour ago, it will be announced/awarded as soon as the hour is up.
legendary
Activity: 2072
Merit: 1001
The current round of 5+ hours is normal then? Once it gets that long I start to worry something is screwy
even though I realize a 10 million share round ain't impossible.
legendary
Activity: 1750
Merit: 1007
US West has been taken offline.  The website will also be relocating this weekend.  The new EU (DE) cluster has been expanded more as well to keep everything running smoothly.
full member
Activity: 154
Merit: 100
    I think you are misunderstanding my situation.  I am limited to ~200MB per 24h or my connection will be grounded to a near halt.(This limit is not just on my miners and includes normal data consumption)

    Here might be some insight...

    Rough calculation:

    Now:
    --------
    One request: 300 bytes of HTTP request, 700 bytes of data ==> ~1 kB of data every 5 seconds for each worker. It is 12kB per minute per worker.

    Json over TCP:
    --------
    One request: (approx) 20 bytes of request, 300? bytes of response EVERY MINUTE ==> 320 bytes per minute per worker.

    By very simple optimization, you cut bandwidth to 2.5% of original size. Without any binary fiddling and proprietary stuff. How many % will be the savings between Json over TCP and binary over TCP?[/list]

    AFAIK, most pools are still using HTTP method.  So you're looking at about 17.3MB per worker, per 24 hours.

    Possibly using some sort of compression-enabled tunnel *might* be able to shave some bandwidth, but I wouldn't expect anything more than 30% savings.

    Cheers,
    Kermee
    sr. member
    Activity: 418
    Merit: 250
    It would be plaintext usernames and passwords followed by random SHA256 hashes.  So about 50% of it would be compressible and I think the hashes wouldn't compress well; very interesting idea though
    hero member
    Activity: 784
    Merit: 1009
    firstbits:1MinerQ
    Perhaps you could setup a compressed link. A proxy at your end doing compression and a vps server on the net decompressing and relaying to the pool. I have a server that's very underutilized and could help if you wanted to test.

    I have no idea if the bitcoin data would compress well or not. That would be the first step - determine if the protocol data compresses well. You may be able to cut down it's size significantly or not at all, depending on the data.

    This could be as simple as an ssh tunnel which has gzip compression enabled - though I wonder how much overhead that would add.

    On Linux this would be simple to test. On Windows you could use the well known Putty client to open a proxy tunnel easily too.
    legendary
    Activity: 2072
    Merit: 1001
    P.P.S. Do you know if it is possible to set up my miners to run through a central computer to your pool or if that would even decrease MB consumption?

    I guess I would use a mining proxy and put all the miners under one username...
    I would not run the bitcoin client 24 hours a day.
    If you are really savvy you could also try shaping your connection to only allow a very slow speed with
    low latency that would cap them.. but always allow communication to go through. No more bursting...

    Neither of these will help.

    Increasing the difficulty of a share is the only thing that will help.  You can also check on Luke-Jr, he is working on some changes to the mining protocol, but I don't think it will help much in this situation.

    Finding a cheap colo or a better internet connection seems like the best answer.  Or, and I hate to even suggest it, but maybe mining isn't ever going to be practical where he is.

    thanks for posting that. i was just throwing out suggestions.. but it appears they were not very useful at all.
    kjj
    legendary
    Activity: 1302
    Merit: 1026
    P.P.S. Do you know if it is possible to set up my miners to run through a central computer to your pool or if that would even decrease MB consumption?

    I guess I would use a mining proxy and put all the miners under one username...
    I would not run the bitcoin client 24 hours a day.
    If you are really savvy you could also try shaping your connection to only allow a very slow speed with
    low latency that would cap them.. but always allow communication to go through. No more bursting...

    Neither of these will help.

    Increasing the difficulty of a share is the only thing that will help.  You can also check on Luke-Jr, he is working on some changes to the mining protocol, but I don't think it will help much in this situation.

    Finding a cheap colo or a better internet connection seems like the best answer.  Or, and I hate to even suggest it, but maybe mining isn't ever going to be practical where he is.
    legendary
    Activity: 2072
    Merit: 1001
    I think you are misunderstanding my situation.  I am limited to ~200MB per 24h or my connection will be grounded to a near halt.(This limit is not just on my miners and includes normal data consumption)

    Then I guess it would be nice to know how much the miners are using versus your other internet use?
    How many MB do the miners use in a day for how many video cards/PCs?

    And you must realize that you are in a very unique situation and cutting down bandwidth was not the goal of diff 2 shares.

    Each miner uses about ~36MB per day.

    I know my I'm in a very unique situation.  I'm not whining, complaining, or otherwise pitifully begging, I'm just asking if eleuthria ever plans on implementing difficulty 2 or >2 shares.

    I think you are misunderstanding my situation.  I am limited to ~200MB per 24h or my connection will be grounded to a near halt.(This limit is not just on my miners and includes normal data consumption)

    I'm sorry, but at this time I do not plan on returning to the plan of implementing diff=2 shares.  The downstream bandwith would be basically the same on your end, only the upstream would be reduced.  I can't imagine what kind of terrible ISP you have that has bandwith caps at 6 GB/month, unless you're mining on a cell phone plan?


    In other news, the EU (DE) cluster just doubled in size.  I'm moving US West miners to that server at this time, in an attempt to save on costs while improving overall pool performance.
    Thanks for letting me know, I guess I'll have to figure something else out.

    P.S. It's not a cell phone plan I'm just in a place where it's really hard to get a decent internet connection.

    P.P.S. Do you know if it is possible to set up my miners to run through a central computer to your pool or if that would even decrease MB consumption?

    I guess I would use a mining proxy and put all the miners under one username...
    I would not run the bitcoin client 24 hours a day.
    If you are really savvy you could also try shaping your connection to only allow a very slow speed with
    low latency that would cap them.. but always allow communication to go through. No more bursting...
    hero member
    Activity: 533
    Merit: 500
    ^Bitcoin Library of Congress.
    I think you are misunderstanding my situation.  I am limited to ~200MB per 24h or my connection will be grounded to a near halt.(This limit is not just on my miners and includes normal data consumption)

    Then I guess it would be nice to know how much the miners are using versus your other internet use?
    How many MB do the miners use in a day for how many video cards/PCs?

    And you must realize that you are in a very unique situation and cutting down bandwidth was not the goal of diff 2 shares.

    Each miner uses about ~36MB per day.

    I know my I'm in a very unique situation.  I'm not whining, complaining, or otherwise pitifully begging, I'm just asking if eleuthria ever plans on implementing difficulty 2 or >2 shares.

    I think you are misunderstanding my situation.  I am limited to ~200MB per 24h or my connection will be grounded to a near halt.(This limit is not just on my miners and includes normal data consumption)

    I'm sorry, but at this time I do not plan on returning to the plan of implementing diff=2 shares.  The downstream bandwith would be basically the same on your end, only the upstream would be reduced.  I can't imagine what kind of terrible ISP you have that has bandwith caps at 6 GB/month, unless you're mining on a cell phone plan?


    In other news, the EU (DE) cluster just doubled in size.  I'm moving US West miners to that server at this time, in an attempt to save on costs while improving overall pool performance.
    Thanks for letting me know, I guess I'll have to figure something else out.

    P.S. It's not a cell phone plan I'm just in a place where it's really hard to get a decent internet connection.

    P.P.S. Do you know if it is possible to set up my miners to run through a central computer to your pool or if that would even decrease MB consumption?
    legendary
    Activity: 1750
    Merit: 1007
    I think you are misunderstanding my situation.  I am limited to ~200MB per 24h or my connection will be grounded to a near halt.(This limit is not just on my miners and includes normal data consumption)

    I'm sorry, but at this time I do not plan on returning to the plan of implementing diff=2 shares.  The downstream bandwith would be basically the same on your end, only the upstream would be reduced.  I can't imagine what kind of terrible ISP you have that has bandwith caps at 6 GB/month, unless you're mining on a cell phone plan?


    In other news, the EU (DE) cluster just doubled in size.  I'm moving US West miners to that server at this time, in an attempt to save on costs while improving overall pool performance.
    legendary
    Activity: 2072
    Merit: 1001
    I think you are misunderstanding my situation.  I am limited to ~200MB per 24h or my connection will be grounded to a near halt.(This limit is not just on my miners and includes normal data consumption)

    Then I guess it would be nice to know how much the miners are using versus your other internet use?
    How many MB do the miners use in a day for how many video cards/PCs?

    And you must realize that you are in a very unique situation and cutting down bandwidth was not the goal of diff 2 shares.
    hero member
    Activity: 533
    Merit: 500
    ^Bitcoin Library of Congress.
    I think you are misunderstanding my situation.  I am limited to ~200MB per 24h or my connection will be grounded to a near halt.(This limit is not just on my miners and includes normal data consumption)
    legendary
    Activity: 2072
    Merit: 1001
    Are you planning on implementing difficulty 2 or >2 shares soon?  I was really looking forward to that feature when you first announced it.

    P.S. Thanks for the great pool.(soon to be absolutely amazing once the pool's luck improves Grin)

    I doubt he will because load is not such a big deal anymore. The code, pushpoold i think it is called, has now
    been optimized to handle much more load then before.

    You are misunderstanding my motive for difficulty 2 or >2 shares.  I desire to have this feature so it will lower MY bandwidth usage.(I'm running on limited bandwidth per 24 section Tongue Cry)  If eleuthria will implement difficulty 2 or >2 shares, then I can run more computers on his pool without having to worry about my internet being ground to a near halt. Cheesy

    I think you are the first person to ever complain about bandwidth usage when it comes to mining. One could get away with 10 computers
    on a 128K ISDN line and i doubt it would stress it much. Low latency is more of a key then a fat pipe.

    But i can be wrong. I will admit I am not graphing my switch ports my miners are connected to. I consider the bandwidth they use
    to be trivial.

    So to implement diff 2 shares because you are on dialup?
    hero member
    Activity: 533
    Merit: 500
    ^Bitcoin Library of Congress.
    Are you planning on implementing difficulty 2 or >2 shares soon?  I was really looking forward to that feature when you first announced it.

    P.S. Thanks for the great pool.(soon to be absolutely amazing once the pool's luck improves Grin)

    I doubt he will because load is not such a big deal anymore. The code, pushpoold i think it is called, has now
    been optimized to handle much more load then before.

    You are misunderstanding my motive for difficulty 2 or >2 shares.  I desire to have this feature so it will lower MY bandwidth usage.(I'm running on limited bandwidth per 24 section Tongue Cry)  If eleuthria will implement difficulty 2 or >2 shares, then I can run more computers on his pool without having to worry about my internet being ground to a near halt. Cheesy
    Pages:
    Jump to: