Opening dozens of tabs...
in
5 posts,
3 voices
Chicago_gang...
Scriptwright
  |
When you open, say, 30 tabs and "go play outside" (or to bed), the browser reloads a page every 2 seconds. Not only does this waste your and RapidShare's bandwidth, but also increases memory leak. (All Greasemonkey scripts cause memory leak for some reason.) And if you have about 20 add-ons (like I used to) and therefore a "heavy" Firefox, it gets even worse. Last time I did this, my Firefox got out of control. When I returned, Firefox said this script had stopped responding and suggested to stop its execution, but clicking "Stop" didn't work; the page file usage (which on my PC is normally about 300Mb) had reached 2Gb and kept growing intensively. So I had to force-close Firefox via Ctrl+Alt+Del. I've found ways to solve these problems, and want to share it with other users who may have experienced similar problems: Firstly, I created a separate Firefox profile specifically for this script. I don't use it for anything else. It has only 1 add-on (Greasemonkey) and only this script (as opposed to my default profile); and I've disabled all plug-ins. I can run it "in the background" in addition to my default Firefox. And I've created a separate shortcut to it. When memory usage of my default Firefox increases (usually, due to memory leaks of other Greasemonkey scripts) to the point when I feel the need restart it, I can do so without interrupting the file download process. In other words, you can simultaneously run multiple Firefoxes that are absolutely independent from each other. (To learn how to do it, read the above-referenced articles and the relevant articles they link to.) I've also created a couple of more profiles with different sets of add-ons for different purposes, so my default Firefox now isn't that heavy any more... Next, I edit the script and set the waiting time (at the top of the script) to about 2/3 of the number of tabs. Usually I open about 40 tabs for the night and set the delay to about 25 minutes. This prevents the browser from reloading a page every 2 seconds. When I return, there are still about 10 tabs to be processed. I deliberately open more tabs than needed so that the average delay doesn't increase to 20-25 minutes. (The thing is, the more tabs get successfully processed, the more the average delay will become. But with about 10 tabs and 25 minutes, the average delay by the end of the night is about 2-5 minutes, which is OK.) As you probably guessed, the next problem with what I described above is that when you click on 40 links to open 40 tabs, the script waits about 25 minutes and reloads all 40 tabs almost at the same time, then it waits another 25 minutes and reloads all 40 tabs at the same time again, and so on. Obviously, this is not what we want because the average delay we need is a couple of minutes, not 25. (As you guessed, by "average delay" I actually meant average of the "general" delay, i.e. the period in which the browser reloads any of the tabs.) So, we need to "desynchronise" the tabs. To achieve it, I set the randomness (currently ±5 seconds) to ±20% of the waiting time (you can use a higher number here but I wouldn't recommend more than 30%). After a couple of runs (20-30 minutes), the tabs get "desynchronised". A given page gets reloaded after random intervals around 25 minutes but the average waiting time of the browser decreases to a few minutes. I'd suggest the author to change it for all users, by replacing this: w = w + Math.ceil(Math.random()*11 - 6); // +-5 secondswith this: w = w + 2*Math.ceil(Math.random()*w*0.2) - Math.round(w*0.2); // +-20%where "0.2" is the percentage (20%). You can play with all the parameters I described (e.g., the number of tabs you need to open, the waiting time, the randomness) to find the best values for your configuration. I guess your RapidShare download speed is the determinative factor here. Hope this helps. EDIT: I should note that I haven't managed to try Koadk's methods yet. |
Kodak
User
|
I'm working on Google Gears version instead of cookies (which are sent to RS). I also plan additional gears-based features: storage files queue (not based on atual tabs) so only one/two windows will be necessary at the end.
|
|
Kodak
User
|
Here it is http://rsaw-clone.googlecode.com/files/rapidsha...
|
iampete
Script's Author
 |
Hi.. thanks to Chicago_gangster for the interesting solution with multiple firefox profiles.. fortunately I haven't been forced to use it yet. I have added the "wait exact time" feature, so this should help to save the bandwidth a little. And big thanks to Kodak for the promising google gears implementation. Looking forward to more ideas from you;-) -PeTe |
|
Kodak
User
|
Thanks for many "thanks" :) I just love playing with javascript.
|
