Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If a file takes <1 second we're not getting paralllization benefits #8

Open
pcn opened this issue Jun 29, 2013 · 2 comments
Open

If a file takes <1 second we're not getting paralllization benefits #8

pcn opened this issue Jun 29, 2013 · 2 comments

Comments

@pcn
Copy link
Owner

pcn commented Jun 29, 2013

In the relay daemon it may make sense to write to multiple temp files and rename them all at once in order to get parallel deliveries.

@pcn
Copy link
Owner Author

pcn commented Jul 1, 2013

Probably use open_next_queue_file to open a configurable number of files, and return a file-like object (though maybe one that's just duck-type file-like enough - e.g. with a write and flush method). That method can write lines round-robin between multiple files and I can measure the speed increase there.

@pcn
Copy link
Owner Author

pcn commented Sep 6, 2013

This is partially working in new_sending_mechanism, but it is broken there. In production_spooling the code prior to this work is bundled up and working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant