Oops. My bad, I'm actually on a 6 Megabit/s down 768 kilobit/s up connection Don't know where that 1.5MB/s number came from. But 600 of (a maximum on a *good* day) 750 kB/s isn't bad, I'd say.
--Your hardware (disk capacity and speed, amount of RAM, and CPU power)
--Your OS
--What you're downloading (number of files mostly)
Some sweeping generalities and my settings, though:
Uncheck "friendly hash checking" if you have a modern processor.
Keep "max open files..." pretty low. Unless you're downloading a huge direcory of images or something, or have (for whatever, probably retarded, reason) dozens of torrents open at once. I have mine set to 100. Some people say to keep this high (1000-10000) if you're running linux, as "everything is treated as a file". This is true, but from what I've seen, this setting is just for downloaded files, not application files/sockets/whatever. Setting it higher than 1000 seems to make things unstable, at least in past versions. Mine is at 100 (Gentoo x86_64) and regularly getting speeds 450kB/s and peaking at about 600kB/s on an Adelphia 1.5MB/768kb cable connection. Apparently that's "awesome".
The next two options default to 0 (unlimited), I think. The first, "max outstanding disk block writes" will limit the amount of data that is kept in RAM after being downloaded before it is written to disk. The only reason you'd really want to mess with this is if your hard disk is slow (you're not running on a floppy RAID, are you?). Or you're a memory miser. If you want a small footprint and have a quick disk, maybe try setting this at... I don't know... 128-ish. That means the write queue (space in memory for temporary storage of fresh downloads before being written to disk) is limited to 2MB. But if your disk can't keep up, downloads will be put on hold. I leave this at 0 (unlimited).
Before pieces are written to disk, they are checked. If you have a modern CPU, you don't need to worry about the "max outstanding check pieces" option... unless you're a retarded memory whore. I leave this at 0 (unlimited), but if you REALLY want to keep Azureus from getting the most out of your system, set this at 10-50-ish. This limits the number of pieces able to be held before checking them. If complete, they go to the write queue. If you run out of room for your downloaded pieces to go because your CPU can't work quickly enough, your downloads will wait. Piece size varies greatly between torrents, so this setting has a varying... impact.
If you want to just read/write from/to files directly, uncheck "enable disk cache". This will have the single largest effect on memory usage. I have it checked. That means that my downloads are held in memory until it is convienient to write to my disk. That also means that what I'm uploading is held in memory, so that I don't need to access the disk each time I upload the same piece to a different person. This setting makes your system more responsive in exchange for a ("large", ~100-200MB) chunk of RAM. Unchecking this greys out the rest of the options.
Of the next two, one is explained in a paragraph next to it, and the other is obvious. Mine are set to 32 and 1024.
Check the first of the three boxes at the bottom. Its a no brainer. It'll pre-read the files you're uploading into RAM as you go, if your disk is idle. The second will use a buffer to reduce disk accesses. Check it. And unless you're having problems/developing, uncheck the last.
I know there are some options not available to certain OSes, but I've only used the latest Azureus from my Gentoo box.
Not really, because those settings depend on:
--Your hardware (disk capacity and speed, amount of RAM, and CPU power)
--Your OS
--What you're downloading (number of files mostly)
Some sweeping generalities and my settings, though:
Uncheck "friendly hash checking" if you have a modern processor.
Keep "max open files..." pretty low. Unless you're downloading a huge direcory of images or something, or have (for whatever, probably retarded, reason) dozens of torrents open at once. I have mine set to 100. Some people say to keep this high (1000-10000) if you're running linux, as "everything is treated as a file". This is true, but from what I've seen, this setting is just for downloaded files, not application files/sockets/whatever. Setting it higher than 1000 seems to make things unstable, at least in past versions. Mine is at 100 (Gentoo x86_64) and regularly getting speeds 450kB/s and peaking at about 600kB/s on an Adelphia 1.5MB/768kb cable connection. Apparently that's "awesome".
The next two options default to 0 (unlimited), I think. The first, "max outstanding disk block writes" will limit the amount of data that is kept in RAM after being downloaded before it is written to disk. The only reason you'd really want to mess with this is if your hard disk is slow (you're not running on a floppy RAID, are you?). Or you're a memory miser. If you want a small footprint and have a quick disk, maybe try setting this at... I don't know... 128-ish. That means the write queue (space in memory for temporary storage of fresh downloads before being written to disk) is limited to 2MB. But if your disk can't keep up, downloads will be put on hold. I leave this at 0 (unlimited).
Before pieces are written to disk, they are checked. If you have a modern CPU, you don't need to worry about the "max outstanding check pieces" option... unless you're a retarded memory whore. I leave this at 0 (unlimited), but if you REALLY want to keep Azureus from getting the most out of your system, set this at 10-50-ish. This limits the number of pieces able to be held before checking them. If complete, they go to the write queue. If you run out of room for your downloaded pieces to go because your CPU can't work quickly enough, your downloads will wait. Piece size varies greatly between torrents, so this setting has a varying... impact.
If you want to just read/write from/to files directly, uncheck "enable disk cache". This will have the single largest effect on memory usage. I have it checked. That means that my downloads are held in memory until it is convienient to write to my disk. That also means that what I'm uploading is held in memory, so that I don't need to access the disk each time I upload the same piece to a different person. This setting makes your system more responsive in exchange for a ("large", ~100-200MB) chunk of RAM. Unchecking this greys out the rest of the options.
Of the next two, one is explained in a paragraph next to it, and the other is obvious. Mine are set to 32 and 1024.
Check the first of the three boxes at the bottom. Its a no brainer. It'll pre-read the files you're uploading into RAM as you go, if your disk is idle. The second will use a buffer to reduce disk accesses. Check it. And unless you're having problems/developing, uncheck the last.
I know there are some options not available to certain OSes, but I've only used the latest Azureus from my Gentoo box.
If you're really concerned about how much of your resources Azureus is using, change some settings. You probably have too many open files or too large a write/check queue. Options > Files > Performance Options. The write and check queues default to unlimited. Also, you may want to uncheck the box for "Cache downloaded data...".
It's not even really a matter of preventing privacy. They finally can implement "Pay-Per-View" everything, and it's their wet-dream. They aren't going to abandon it.
That is EXACTLY right. It's not about being pissed off at all the filesharers out there cutting into (already astronomical) profits, its about squeezing more money out of the gullible, legit consumers. Making filesharing harder and forcing more legit consumers is just a side benefit. Hell, *I'd* try to do it if I was in their shoes, but that doesn't make it right.
I'm no rocket scientist, but I would guess it would be time from the launch. "T minus three, two, one... blastoff!" And then events happen at like, T four days six hours or whatever.
I know a lot of people here *hate* anime and anyone who likes it, but...
Has anyone seen Battle Programmer Shirase? There was an episode where this super retardedly awesome programmer (Shirase, the main character) hacks three neglected satellites and crashes them in a line to target a boat. The first in line acted as a primary heat shield for the second two and evaporated pretty quick, the second did the same for the last, and the last plowed right into the boat in a big explosion.
My Gentoo Box boots in 13 seconds. Maybe 5 seconds to fluxbox, including loging in and "startx". Not a big deal, and I restart a whole once or twice a week. But that's because I'm moving hard disks around and only have one firewire case. When I do restart, I don't want to have remnants from last time, I want to start over. I thought that was the point of restarting. I for one am not going to rush out to buy anything to cut ten seconds off my boot time anytime soon. My two cents, flame me or mod me down for being a dumbass, I don't particularly care. Oh, and I didn't bother to RTFA. Bite me.
Slashdot Mirror
Oops. My bad, I'm actually on a 6 Megabit/s down 768 kilobit/s up connection Don't know where that 1.5MB/s number came from. But 600 of (a maximum on a *good* day) 750 kB/s isn't bad, I'd say.
D'oh! Let's try that again.
Not really, because those settings depend on:
--Your hardware (disk capacity and speed, amount of RAM, and CPU power)
--Your OS
--What you're downloading (number of files mostly)
Some sweeping generalities and my settings, though:
Uncheck "friendly hash checking" if you have a modern processor.
Keep "max open files..." pretty low. Unless you're downloading a huge direcory of images or something, or have (for whatever, probably retarded, reason) dozens of torrents open at once. I have mine set to 100. Some people say to keep this high (1000-10000) if you're running linux, as "everything is treated as a file". This is true, but from what I've seen, this setting is just for downloaded files, not application files/sockets/whatever. Setting it higher than 1000 seems to make things unstable, at least in past versions. Mine is at 100 (Gentoo x86_64) and regularly getting speeds 450kB/s and peaking at about 600kB/s on an Adelphia 1.5MB/768kb cable connection. Apparently that's "awesome".
The next two options default to 0 (unlimited), I think. The first, "max outstanding disk block writes" will limit the amount of data that is kept in RAM after being downloaded before it is written to disk. The only reason you'd really want to mess with this is if your hard disk is slow (you're not running on a floppy RAID, are you?). Or you're a memory miser. If you want a small footprint and have a quick disk, maybe try setting this at... I don't know... 128-ish. That means the write queue (space in memory for temporary storage of fresh downloads before being written to disk) is limited to 2MB. But if your disk can't keep up, downloads will be put on hold. I leave this at 0 (unlimited).
Before pieces are written to disk, they are checked. If you have a modern CPU, you don't need to worry about the "max outstanding check pieces" option... unless you're a retarded memory whore. I leave this at 0 (unlimited), but if you REALLY want to keep Azureus from getting the most out of your system, set this at 10-50-ish. This limits the number of pieces able to be held before checking them. If complete, they go to the write queue. If you run out of room for your downloaded pieces to go because your CPU can't work quickly enough, your downloads will wait. Piece size varies greatly between torrents, so this setting has a varying... impact.
If you want to just read/write from/to files directly, uncheck "enable disk cache". This will have the single largest effect on memory usage. I have it checked. That means that my downloads are held in memory until it is convienient to write to my disk. That also means that what I'm uploading is held in memory, so that I don't need to access the disk each time I upload the same piece to a different person. This setting makes your system more responsive in exchange for a ("large", ~100-200MB) chunk of RAM. Unchecking this greys out the rest of the options.
Of the next two, one is explained in a paragraph next to it, and the other is obvious. Mine are set to 32 and 1024.
Check the first of the three boxes at the bottom. Its a no brainer. It'll pre-read the files you're uploading into RAM as you go, if your disk is idle. The second will use a buffer to reduce disk accesses. Check it. And unless you're having problems/developing, uncheck the last.
I know there are some options not available to certain OSes, but I've only used the latest Azureus from my Gentoo box.
Not really, because those settings depend on: --Your hardware (disk capacity and speed, amount of RAM, and CPU power) --Your OS --What you're downloading (number of files mostly) Some sweeping generalities and my settings, though: Uncheck "friendly hash checking" if you have a modern processor. Keep "max open files..." pretty low. Unless you're downloading a huge direcory of images or something, or have (for whatever, probably retarded, reason) dozens of torrents open at once. I have mine set to 100. Some people say to keep this high (1000-10000) if you're running linux, as "everything is treated as a file". This is true, but from what I've seen, this setting is just for downloaded files, not application files/sockets/whatever. Setting it higher than 1000 seems to make things unstable, at least in past versions. Mine is at 100 (Gentoo x86_64) and regularly getting speeds 450kB/s and peaking at about 600kB/s on an Adelphia 1.5MB/768kb cable connection. Apparently that's "awesome". The next two options default to 0 (unlimited), I think. The first, "max outstanding disk block writes" will limit the amount of data that is kept in RAM after being downloaded before it is written to disk. The only reason you'd really want to mess with this is if your hard disk is slow (you're not running on a floppy RAID, are you?). Or you're a memory miser. If you want a small footprint and have a quick disk, maybe try setting this at... I don't know... 128-ish. That means the write queue (space in memory for temporary storage of fresh downloads before being written to disk) is limited to 2MB. But if your disk can't keep up, downloads will be put on hold. I leave this at 0 (unlimited). Before pieces are written to disk, they are checked. If you have a modern CPU, you don't need to worry about the "max outstanding check pieces" option... unless you're a retarded memory whore. I leave this at 0 (unlimited), but if you REALLY want to keep Azureus from getting the most out of your system, set this at 10-50-ish. This limits the number of pieces able to be held before checking them. If complete, they go to the write queue. If you run out of room for your downloaded pieces to go because your CPU can't work quickly enough, your downloads will wait. Piece size varies greatly between torrents, so this setting has a varying... impact. If you want to just read/write from/to files directly, uncheck "enable disk cache". This will have the single largest effect on memory usage. I have it checked. That means that my downloads are held in memory until it is convienient to write to my disk. That also means that what I'm uploading is held in memory, so that I don't need to access the disk each time I upload the same piece to a different person. This setting makes your system more responsive in exchange for a ("large", ~100-200MB) chunk of RAM. Unchecking this greys out the rest of the options. Of the next two, one is explained in a paragraph next to it, and the other is obvious. Mine are set to 32 and 1024. Check the first of the three boxes at the bottom. Its a no brainer. It'll pre-read the files you're uploading into RAM as you go, if your disk is idle. The second will use a buffer to reduce disk accesses. Check it. And unless you're having problems/developing, uncheck the last. I know there are some options not available to certain OSes, but I've only used the latest Azureus from my Gentoo box.
If you're really concerned about how much of your resources Azureus is using, change some settings. You probably have too many open files or too large a write/check queue. Options > Files > Performance Options. The write and check queues default to unlimited. Also, you may want to uncheck the box for "Cache downloaded data...".
I'm no doctor, but couldn't you just take some samples of all his fluids and intoduce it to each of them?
It's not even really a matter of preventing privacy. They finally can implement "Pay-Per-View" everything, and it's their wet-dream. They aren't going to abandon it.
That is EXACTLY right. It's not about being pissed off at all the filesharers out there cutting into (already astronomical) profits, its about squeezing more money out of the gullible, legit consumers. Making filesharing harder and forcing more legit consumers is just a side benefit. Hell, *I'd* try to do it if I was in their shoes, but that doesn't make it right.
I'm no rocket scientist, but I would guess it would be time from the launch. "T minus three, two, one... blastoff!" And then events happen at like, T four days six hours or whatever.
I know a lot of people here *hate* anime and anyone who likes it, but...
Has anyone seen Battle Programmer Shirase? There was an episode where this super retardedly awesome programmer (Shirase, the main character) hacks three neglected satellites and crashes them in a line to target a boat. The first in line acted as a primary heat shield for the second two and evaporated pretty quick, the second did the same for the last, and the last plowed right into the boat in a big explosion.
My Gentoo Box boots in 13 seconds. Maybe 5 seconds to fluxbox, including loging in and "startx". Not a big deal, and I restart a whole once or twice a week. But that's because I'm moving hard disks around and only have one firewire case. When I do restart, I don't want to have remnants from last time, I want to start over. I thought that was the point of restarting. I for one am not going to rush out to buy anything to cut ten seconds off my boot time anytime soon. My two cents, flame me or mod me down for being a dumbass, I don't particularly care. Oh, and I didn't bother to RTFA. Bite me.
:)
AMD Athlon 64 3000+ Venice / 2G / 1.8T over 8 disks... mostly anime.
I second that. This whole f'ing thing is retarded.
I heard somewhere that they don't work at all and emit ozone.
Eh...Alphakat. D'oh.
I hope you're kidding. That was a hoax based on Dr. Christian Koch's company's name -- Aplhakat. Even The Week ran a blurb about it, though.