Sorry for this question but loopline, do you own Scrapebox? It seems sweetfunny (the OP) is not posting here so I was wondering who the real owner is.
No I do Not own/work for scrapebox. Sweetfunny along with someone else is partners in Scrapebox. Sweetfunny stated a long time ago they don't reply to this thread much because they put all their time into support and development of the program. I mean they sell a easily $300 program for $57 so to even give support in the first place is huge bonus. I actually came about scrapebox in a difficult time in my life. I wound up making a lot of money off of it, and always got awesome free support and a bunch of the features in scrapebox are there simply because I requested them. So I am pretty loyal to scrapebox and am happy to post here a lot and help out. It saves the developer time and I then they can focus on development and other things.
Thanks again Matt, more thought provoking info, really appreciate it.
Do you use a vpn when posting? I would imagine that could cause
a bottleneck for traffic.
I'm thinking harvesting takes up considerably more resources than
just posting is that right?
Also, how many connections can you make all together from the gigenet
server you have? Assuming we have good proxies allowing say 100 connections
per proxy, can you talk more about the benefits of running multiple
instances of scrapebox (100-200 connections each) as opposed to running
fewer instances with more proxies? Do you run more instances to handle
more projects at a time?
Also, I'm a little confused about this...
"If you had 500 private proxies from 5 different providers (to maximize your max simultaneous connections) and you put it on 500 connections you would prob blow thru 60K in 30 mins."
This equates to only 1 connection per proxy, should I not be trying to
get about 80 connections per proxy if the proxy can handle 100 connections?
Thanks again for all your advice!
I don't personally typically use a VPN when posting. I have tested HMA in the past and it works and all, but I have private proxies and those are faster. A VPN may or may not slow things down. The upside to a vpn is that you don't need proxies, as long as the vpn provider is cool with that. The down side of course, is that you are subject to the limitations of the vpns internet connection and their dns speeds.
As for harvesting resources, I would say generally the opposite. Assuming by resources you mean bandwidth, processor, RAM, etc... then harvesting would take the least. Largely because you connecting to companies whos business is providing resources and they are masters are doing so with using the least overhead in need for bandwidth, processor, etc.. I mean look at googles pages, no flash, bearly any images, no clutter, etc... so something like fast poster or the link extractor or something that is loading user generated pages full of gaudy flash and various other things, maybe 50K comments on a blog engine page etc... A blog engine page might be 10MB+ to load while a 100 results page for google would be in the Kbs.
I try to keep the gigenet server at a max of 1000-2000 connections. The physical machine isn't so much the limits as its top notch. At that point your dealing with windows messaging and windows is simply Not good at dealwith massive scale connections larger then that. An "ideal" setup for windows is probably more in the 1000 connections range, but I haven't really had issues running 10 instances of scrapebox at 200 connections each totaling out 2000 simultaneous connections. I have solidly pushed 300-400Mbit of bandwidth for extended periods of time.
The truth of the matter is that a server such as we are talking about is highly capable. I used to spend $1500 a month just on servers and proxies. However I have cut that back to under $1000 monthly at this point. Simply by working smarter not harder. I have made great strides to laser toning my skills a making footprints and scraping smarter. In turn at building custom filters in my external applications to filter lists on my server. Then when I post I am not posting to near as much as I used to be. I still work with large volumes of urls, but used to I might tear thru post to 26 million urls to make an AA list. No with better scraping, server side filtering and efficiency it might do the same list with only a few million urls. (yes I make big lists, like Im siting on about 400K AA at the moment and still going).
To that end, if you are up for the learning, its just worth your time to make sure your efficient at what your doing. I do still use multiple instance. I have noticed windows "seems" to not like more then 10 instances of scrapebox running per desktop. I don't fully know why, and I don't completely care, but if I need to run say 20 instances, Ill just create another user/desktop on the server. Watching the resources and crashes it seems to work out better this way - For what thats worth anyway.
What I actually do is pin all my instances to the desktop and number them 1-10. Then I load open office Calc (excel equiv but free) on the server and list out all the instances and keep a running tab of what they are doing. I "typically" am routine. Ill have say instances 1,3,5 doing commenting, 2,4,6 doing trackbacks, 7 doing other things like pr checking etc.. 8,9 and 10 for more "whatever I need at the moment" etc... I don't hold exactly to that of course, but you get the point. I just keep it organized so I am as efficient as possible.
Now that I rambled about that, Im not completely sure I answered your question, did I? About benefits I mean. Perhaps you meant from a connection standpoint. Windows seems to like to deal with about max of 200 connections per instance of scrapebox. Setting it higher tends to reduce success rates, so I usually keep my connections at 200 or less per instance and divide what I Am doing among instances if I need to do more connections now.
~~~
on proxies, most providers don't limit it to 100 connections "per proxy" they limit it to 100 connections per the group of proxies they give you. So if they give you 10 proxies, its generally limited to 100 connections spread between any of those 10 proxies. They don't really care if you put all 100 at 1 proxy and ignore the other 9, its just about maintaining integrity for them. Most proxy providers are about efficiency, so they may have a vps running with a full block of 254 IPs and all 10 of your proxies might come from that same vps, while of course two dozen other users 10 proxies also share the vps with you. Think that thru. They are private proxies but if you have 24 people each with 10 proxies from teh same vps and that vps is running a 100mbit connection and all 24 people are trying to push data thru those proxies at once. your getting less then 10mbit per user, and say your on a 1Gbit line hammering on posting with those proxies, your 1gbit line is bottlenecked down to 10mbit because thats the max the proxy is going to give you.
This boils down to, at least in the proxy world, YOU GET WHAT YOU PAY FOR. So that $30 for 10 private proxies might seem pricy vs that $10 somewhere else, but that $10 guy is cutting his expenses by running on a vps 100mbit line and that $30 provider is probably using a dedicated server on a 100-1000mbit line. Too many variables to go into, but you get the point, you need to understand what your providers limitations are exactly to get the best use out of it.
Although if you go fast posting, you can tell. Crank the connections to like 300 and hammer away for 2 mins. Then look at all the error codes. You will see something thats dominate. 403, 407, 404 etc... Something will consume like 80-90% of the error codes. Then turn the connections down to like 50 and do the same list for like 2 mins. Then look at the error code. You should see that error code drastically reduced to only a few percent if not at all. Then you have the error code (s) that your proxy provider gives when your connections are being denied by overloading the proxies. 403 and 407 are common. Then just crank up the connections little by little until you see this error code start to dominate again, and there you have what your proxies can handle.
Matt, about the trackbacks. I was doing a little research on them,
any truth to the idea that there is an increased risk of getting an
ip ban?
Also, should the connection settings be changed to something lower
than one would use while using fast poster? thanks.
IP ban from what? I have posted to millions of trackbacks and not gotten an ip ban. Can you be more specific?
Well caps on trackbacks are 100 connections, but I can easily post at 20 connections and go quicker then a comment run at say 80 connections. So I try to run it at 50-100 connections whenever I can, as Im impatient lol, but its not "needed" to go slower. If functions efficiently at its max of 100 connections, so long as your server/proxies can hack it.