Why just check one file at a time? If possible instantiate multiple pipes for data retrieval. By the looks of it the hardest part on your machine is the writing of the file and that itself could be queued. The requests to the opposing servers could be ratelimited but I feel one request at a time is a bottleneck.
2c,
-a
[REQ] Pipelining/Multirequest
Re: [REQ] Pipelining/Multirequest
Because of MPFreaker's priority system (it prefers album information from particular servers) and our desire to keep MPFreaker from being considered "abusive" by the server's owners, it doesn't gather info for more than one song at a time. "Deep Search" does try to gather information from all servers simultaneously, but still for only one song at a time.
That doesn't mean that we're not looking for ways to speed things up for future versions.
Leon
That doesn't mean that we're not looking for ways to speed things up for future versions.
Leon
Re: [REQ] Pipelining/Multirequest
Thanks Leon. The server argument is a common one, and realistic. What might be nice if the services that we're going to would offer a bulk check or multiline/item feed.beastie wrote:Because of MPFreaker's priority system (it prefers album information from particular servers) and our desire to keep MPFreaker from being considered "abusive" by the server's owners, it doesn't gather info for more than one song at a time. "Deep Search" does try to gather information from all servers simultaneously, but still for only one song at a time.
That doesn't mean that we're not looking for ways to speed things up for future versions.
Of course you still run into their limitations and not wanting bombardment. Something you can only throw more money/machines at.
..dreams on..... they need some distributed network... and on.. heheh