ConfigFiles

From AzureusWiki

(Redirected from FileAllocationMethods)

Jump to: navigation, search

1 Azureus > Tools > Options > Files

[edit]

Azureus > Tools > Options > Files

Currently, Azureus can employ 3 disk-allocation mechanisms:

Pre-allocate: Reserves the entire space on the filesystem, but may actually be using a sparse file (reserved, but not truely allocated), depending on the file-system. This is the Azureus default, when neither Allocate-and-zero nor Incremental are enabled. (~TwelveBaud: Can you be more deterministic? I know Windows 2000 and up support sparse files but you have to ask for them specially; does Azureus poke the FS driver and ask for a sparse file?)

Pre-allocate and zero: Like pre-allocate, but actually writes the entire file full of zeros, forcing the fs to allocate the entire space.

Incremental: File size starts out as 0, then increases to x size when byte x is written: i.e. if the end piece of a torrent is downloaded first, then the entire file size will be used.

There are subtle nuances to the above, depending on the particular fs employed, which I will not get into.

The python clients employ a 4th method by default, which is a more-intelligent form of incremental than what Az currently uses: like incremental, file starts out 0-sized, but when piece x comes in, it's appended to the current file position, even if it doesnt truly belong there. As new pieces come in, they are appended and shuffled around as needed: the file size grows only by 1-piece-size for every new piece written, but the pieces are not necessarily/usually in final order. Azureus will eventually support this form of incremental, but it's a ways off.

Allocate and zero new files on creation.

Checking this option will cause Azureus to reserve a portion of the disk equal to the entire size of the torrent, and fill that space with zeroes. This option will minimize fragmentation of the hard drive in comparison to incremental allocation. If this option is checked, incremental file creation can not be used.

Truncate existing files that are too large.

todo

Enable incremental file creation.

Selecting this option will result in Azureus only reserving as much disk space as is necessary for it to write the latest piece it has received. For example, if it received piece 125 of 1000, it would reserve space up until the point where piece 125 goes in the torrent. If then it received piece 500, then the reserved space would increase, in this example to half the complete size of the torrent. Because you may have several torrents doing this at once, as well as other processes writing to the disk, this method will result in more fragmentation than using pre-allocation. If this option is checked, pre-allocation can not be used.

It is also possible to choose a third method of allocation, pre-allocate w/o zero, by unchecking both 'creation' options. (This is the default allocation method for Azureus.)

Related pages: FileAllocationMethods

Re-check pieces when download is done.

Selecting this option will cause Azureus to recheck the torrent once it has completed to verify the data matches the hash and has not been corrupted somehow. If any piece doesn't pass the error correction, it is simply discarded and downloaded again. This option may cause occasional high CPU usage on slow systems.

Use fast-resume mode.

Fast-Resume mode makes it possible to start and stop torrents without having to always rehash the existing data. It is recommended this feature be left on as it greatly saves time and resources. Fast-resume data is stored in the .torrent file (see below).

Update resume data every X minutes.

Allows you to set how frequently resume data is written to the .torrent file.

Save peer connections for quick reconnects.

When this option is switched on, Azureus caches information about the peers it's connected to and stores it in the .torrent file. This cached information makes it possible to connect to peers and seeders even in the case of the tracker going offline.

Max peers to save.

Sets the maximum number of peer connections to cache (per torrent).

Save to default data directory.

Enter a directory path you would like your torrents to automatically download into. If this option is deselected, Azureus will ask for a download directory each time you start a torrent. If you have activated this option, it's still possible to download a torrent to a different directory by using the File -> Open menu.

Move completed files.
- Directory.

Enter the path to the directory you want torrents to be moved to when they finish downloading and start seeding. Unchecking this option will result in torrents staying in the download directory. It can be hard to tell the difference between finished and incomplete torrents however, so it's recommended they be separated.

- Move .torrent.

Will also move the .torrent file from it's saved location (see below) to the completed files directory. Can be useful to keep track of .torrent files for later reseeding.

- only if in default data directory.

With this checked, the torrent will only be moved to the completed directory if it was originally saved to the default data directory. This is useful if you have certain torrents you want saved somewhere else, otherwise when they finished downloading they'd just get moved into the completed directory with the others.

Auto-prioritize files with extension...

Files inside torrents that have the extensions listed here will automatically be given a priority of High. Individual file priorities can be viewed on the Files tab of the advanced view.

Confirm when deleting data.

Azureus will pop-up a confirmation dialog whenever data is about to be deleted. It's recommended this is left checked. Deleted data does not go to the recycle bin.

[edit]

Files - Torrents

Save .torrent files.
- Save directory.

Enter the directory you want to save your .torrent files in. Whenever Azureus opens a torrent, it will place a copy of the .torrent file in this directory.

- Save backup.

You may want to save a backup of your .torrent files in case something happens to the original. Checking this option will make Azureus place a copy of the .torrent with the extension .bak in your .torrent save directory.

By default add new torrents in a stopped state.

todo

Import new .torrents automatically.

Azureus has the ability to periodically scan a directory and automatically open any .torrents it finds.

Import Directory.

Sets the directory to be monitored.

Interval.

Sets how often to scan the directory for new .torrent files.

Begin stopped.

Will load the torrent in a stopped state rather than queuing it.

Default torrent encoding when selection required.

This option lets you choose a default character set to use. Character sets are a way of displaying languages that use different alphabets such as Russian, Japanese, Chinese, Sanskrit, etc. You may have occasionally come across torrents that appear to have garbage characters in their names. These appear this way because they belong to a different character set than the one you're using, or you don't have the fonts available to render that language.

Always prompt when an encoding choice is available.

Select this to always be asked which encoding to use when multiple choices are available.

Show less likely encodings.

todo

Consider all possible encodings.

todo

Files to ignore when creating torrents.

These files will not be included when making a torrent using Azureus' built in torrent maker. .DS_Store;Thumbs.db should always be included here as they cause all kinds of trouble. This field does not allow wildcards.

[edit]

Files - Torrents - Removal Rules

Unauthorized torrents are those where the announce response from the tracker contains either "not authorized" or "unauthorized". Examples of when you could receive this kind of message are when attempting to download a torrent from a private tracker of which you are not a member or not logged in, or when a torrent is no longer available through the tracker due to removal or some other reason.

Automatically remove unauthorized torrents.

todo

Only if seeding.

todo

Remove Azureus update torrents as the swarm requires

Azureus' auto-update feature works by creating a torrent containing the update, and then connecting Azureus clients to the swarm. Once the update is downloaded it is automatically installed, Azureus is restarted, and the update remains seeding for use by other clients in the swarm. Checking this option will automatically remove the seeding update if the swarm is healthy enough to not require it.

[edit]