|Register||FAQ||The Twelve Commandments||Members List||Calendar||Arcade||Search||Today's Posts||Mark Forums Read|
|New Feature Requests Your idea for a cool new feature. Or, a LimeWire annoyance that has to get changed.|
| Welcome To Gnutella Forums |
You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content, fun aspects such as the image caption contest and play in the arcade, and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! (click here)
If you have any problems with the Gnutella Forum registration process or your Gnutella Forum account login, please contact us (this is not for program use questions.) Your email address must be legitimate and verified before becoming a full member of the forums. Please be sure to disable any spam filters you may have for our website, so that email messages can reach you.
Note: Any other issue with registration, etc., send a Personal Message (PM) to one of the active Administrators: Lord of the Rings or Birdy.
Once registered but before posting, members MUST READ the FORUM RULES (click here) and members should include System details - help us to help you (click on blue link) in their posts if their problem relates to using the program. Whilst forum helpers are happy to help where they can, without these system details your post might be ignored. And wise to read How to create a New Thread
If you are a Spammer click here.
This is not a business advertising forum, all member profiles with business advertising will be banned, all their posts removed. Guests and search engines cannot view member profiles.
Hilfe in Deutsch, . Ayuda en español, . Aide en français . et . LimeWire en français, . Hulp in het Nederlands
Before you post to one of the specific Client Help and Support Conferences in Gnutella Client Forums please look through other threads and Stickies that may answer your questions. Most problems are not new. The Search function is most useful. Also the red Stickies have answers to the most commonly asked questions. (over 90 percent).
If your problem is not resolved by a search of the forums, please take the next step and post in the appropriate forum. There are many members who will be glad to help.
If you are new to the world of file sharing please do not be shy! Everyone was ‘new’ when they first started.
When posting, please include details for:
Your Operating System ....... Your version of your Gnutella Client (* this is important for helping solve problems) ....... Your Internet connection (56K, Cable, DSL) ....... The exact error message, if one pops up
Any other relevant information that you think may help ....... Try to make your post descriptive, specific, and clear so members can quickly and efficiently help you. To aid helpers in solving download/upload problems, LimeWire and Frostwire users must specify whether they are downloading a torrent file or a file from the Gnutella network.
Members need to supply these details >>> System details - help us to help you (click on blue link)
There are senior members on the forums who serve as Moderators. These volunteers keep the board organized and moving.
Moderators are authorized to: (in order of increasing severity)
Move posts to the correct forums. Many times, members post in the wrong forum. These off-topic posts may impede the normal operation of the forum.
Edit posts. Moderators will edit posts that are offensive or break any of the House Rules.
Delete posts. Posts that cannot be edited to comply with the House Rules will be deleted.
Restrict members. This is one of the last punishments before a member is banned. Restrictions may include placing all new posts in a moderation queue or temporarily banning the offender.
Ban members. The most severe punishment. Three or more moderators or administrators must agree to the ban for this action to occur. Banning is reserved for very severe offenses and members who, after many warnings, fail to comply with the House Rules. Banning is permanent. Bans cannot be removed by the moderators and probably won't be removed by the administration.
1. Warez, copyright violation, or any other illegal activity may NOT be linked or expressed in any form. Topics discussing techniques for violating these laws and messages containing locations of web sites or other servers hosting illegal content will be silently removed. Multiple offenses will result in consequences. File names are not required to discuss your issues. If filenames are copyright then do not belong on these forums & will be edited out or post removed. Picture sample attachments in posts must not include copyright infringement.
2. Spamming and excessive advertising will not be tolerated. Commercial advertising is not allowed in any form, including using in signatures.
3. There will be no excessive use of profanity in any forum.
4. There will be no racial, ethnic, or gender based insults, or any other personal attacks.
5. Pictures may be attached to posts and signatures if they are not sexually explicit or offensive. Picture sample attachments in posts must not include copyright infringement.
6. Remember to post in the correct forum. Take your time to look at other threads and see where your post will go. If your post is placed in the wrong forum it will be moved by a moderator. There are specific Gnutella Client sections for LimeWire, Phex, FrostWire, BearShare, Gnucleus, Morpheus, and many more. Please choose the correct section for your problem.
7. If you see a post in the wrong forum or in violation of the House Rules, please contact a moderator via Private Message or the "Report this post to a moderator" link at the bottom of every post. Please do not respond directly to the member - a moderator will do what is required.
8. Any impersonation of a forum member in any mode of communication is strictly prohibited and will result in banning.
9. Multiple copies of the same post will not be tolerated. Post your question, comment, or complaint only once. There is no need to express yourself more than once. Duplicate posts will be deleted with little or no warning. Keep in mind a forum censor may temporarily automatically hold up your post, if you do not see your post, do not post again, it will be dealt with by a moderator within a reasonable time. Authors of multiple copies of same post may be dealt with by moderators within their discrete judgment at the time which may result in warning or infraction points, depending on severity as adjudged by the moderators online.
10. Posts should have descriptive topics. Vague titles such as "Help!", "Why?", and the like may not get enough attention to the contents.
11. Do not divulge anyone's personal information in the forum, not even your own. This includes e-mail addresses, IP addresses, age, house address, and any other distinguishing information. Don´t use eMail addresses in your nick. Reiterating, do not post your email address in posts. This is for your own protection.
12. Signatures may be used as long as they are not offensive or sexually explicit or used for commercial advertising. Commercial weblinks cannot be used under any circumstances and will result in an immediate ban.
13. Failure to show that you have read the forum rules may result in forum rules breach infraction points or warnings awarded against you which may later total up to an automatic temporary or permanent ban. Supplying system details is a prerequisite in most cases, particularly with connection or installation issues.
Violation of any of these rules will bring consequences, determined on a case-by-case basis.
Thank You! Thanks for taking the time to read these forum guidelines. We hope your visit is helpful and mutually beneficial to the entire community.
| ||LinkBack||Thread Tools||Display Modes|
Two-tiered upload slots?
For some strange reason I like to monitor my uploads. I have a cable modem with asymmetric I/O. It really bothers me to see all my upload slots taken by people downloading enormous files, while poor souls wait in the queue for hours to download tiny files.
Is there some way I could download x upload slots for big files (say 10MB and up) and y upload slots for small files (under 10MB--or maybe less--maybe configurable by the user)?
What you're really after is a method of sharing your upload resources such that every gets an equal number of bytes, not an equal number of files.
Is there any scope in giving those grabbing large files perhaps 1 minutes of upload time before popping them back on the tail of the upload queue ? This might be simpler to manage than multiple queues, although could slow the propogation of large files through the gnet.
Of course, what one really wants to do is favour those you're confident will in turn make the file available to others. That's a trust mechanism though, leading down the route of certificates and blacklists. Urgh.
I think an easy solution would be to alter the network in a way so that the uploader could check a box or an option that says "Don't uplaod files larger than x MBs without the download having y sources". So therefore, when someone decides to just download a 600MB file from just one source, thus monopolizing this one source, the uploader could force the downloader to have perhaps 3 sources before downloading the file. More sources will decrease the amount of time any one source is monopolized.
Such an option should definitely have a max so it would not be abused.
Or the above option, the two tiered system would also work well.
I don't want to bump people from the queue. Some of them are on modems or otherwise flaky connections, after all.
What I want is to keep 2 upload slots open for small files--say, 3mb and smaller.
As long as I'm sharing large files, I can't effectively share the smaller files I have. That's a shame. With 2 slots I could go through hundreds of small file shares in an hour. Meanwhile the 300MB fileshares could chug along for hours or days . . . and everyone would be happy.
Example below. To keep things simple only two upload slots exist, and requests come in in equal numbers for each file.
Initially no uploads are happening:
Slot 1: <empty>
Slot 2: <empty>
Requests come in for the two files being shared and uploding starts:
Slot 1: SmallFile(1)
Slot 2: BigFile(1)
More requests arrive and are queued:
Slot 1: SmallFile(1)
Slot 2: BigFile(1)
SmallFile(1) finishes uploading quickly and the next item in the queue starts uploading:
Slot 1: BigFile(2)
Slot 2: BigFile(1)
Now the queued download for smallfile(2) would, under the current scheme, have to wait for the two active uploads of BigFile to complete, even though they might take hours.
To generate a more equal sharing of upload bandwidth, people uploading big files get moved to the tail of the queue after they've downloaded a certain amount - say 5MB. So, after a certain amount of time the downloader of BigFile(1) hits this limit and gets requeued:
Slot 1: SmallFile(2)
Slot 2: BigFile(2)
Note that a queue slot will always exist as one is freed up by moving from the queue to the now available upload slot. SmallFile(2) now gets a chance to upload and BigFile(1) will resume uploading when it's done (or when BigFile(2) has uploaded a certain amount and gets moved back to the tail of the queue).
To within a certain degree of tolerance, this method allows someone to download 20 x 5 MB files in the same time it takes someone to download a single 100MB file, resources are shared equally. The downside is that an oversubscribed server sharing only large files will favour giving everyone some upload time rather than finishing a single upload (and potentially sharing the upload demand with another server). Partial file sharing foils this problem in theory, alas in practise the gnet's far from ideal.
Salut, I asked before for a similar feature:
In the upload window of preferences, as an option: maximum of simultaneous uploads for a same file _ (where by default it would be 2 or 3). The LW client would send a busy to the other clients asking for that file without having to create another queue (à la Shareaza). This is simple to implement and it sould work great with partial file sharing.
Take my vote on that too...
..Amazing! I woke up with the same idea, and I told myself 'this I have to post it in the forum'. The next I see is this topic.
Before getting straight to the point, I want to tell that I am impressed beyond words with the actual Limewire, I remember being in Gnutella from the early days of Gnucleus (maybe before); There was Limewire too, I thought for myself 'well,nice... and pretty, but JAVA, you know... plus, it's slow.' Now I returned today to Gnutella after an exile in closed networks (no, not Fasttrack) and I find all those features previously unthinkable for Gnutella implemented here. And I almost don't believe it. Believe me...
Well, as we know, "large" file downloaders often harm unintentionally "small" file downloaders. Then again, what is "small"? What is "large"?
10 MB. Maybe this size is a large file for music (or e-book.. plain ascii anyway)uploaders. Or a small file for a movie uploader. What if the Limewire user does upload music + movies? Harder to say when is small and when is large... Harder still if you consider what is currently being uploaded. Confused? Fear not...
What we need here is that Limewire analizes the size of the files being uploaded versus the files requested at the queue, and consecuently asign a slot : the larger the file being uploaded (in relation of what you have shared) the smaller the file intended to be uploaded next (there is already an uploading range, so no problem). This way when a large file is being uploaded, a small file must go with it, the "medium" files are uploaded together and we clean a little bit the queue; I know this theory sound a little wacky but I do not recommend to set a fixed cipher as asked previously: the result will probably be extinted files.. and I always thought that balance is the key to filesharing. What do you think about this?
Let's analyse this
To clarify this theory further: If two files matches this judgement and the one finishes before the another, we keep replacing this piece of the puzzle 'till the big one finishes or the download is cancelled. I don't know how well this works in practice, though I think it should do only a small, but perceptively enough difference... Let's pray.
Forgot to mention something...
...What I meant initially is that the two files examplified are to be uploaded simultaneously.
Before you ask, I know that if there is no upload slot free this isn't going to work but anyway is probably better than the way it is: Worst case, it will be the same. Four slots are needed: first two slots should be used with the big-small relation, and the other 2 are to be used in the "mediocres are always together" relation... Thus, graphicating a "cross" of file dependencies.
|Thread||Thread Starter||Forum||Replies||Last Post|
|Upload Slots||Mommosan||Download/Upload Problems||0||December 28th, 2002 06:32 AM|
|upload slots||mrsteve0924||General Gnutella / Gnutella Network Discussion||3||November 7th, 2002 07:12 AM|
|upload slots||mrsteve0924||Open Discussion topics||1||October 26th, 2002 09:30 AM|
|Two-tiered upload system?||Unregistered||General Gnutella / Gnutella Network Discussion||4||July 16th, 2001 10:37 AM|
|Two-tiered upload system?||Unregistered||Site Feedback||0||July 14th, 2001 01:41 PM|