Simple Scan only uses one core when saving PNG-s
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Simple Scan |
Triaged
|
Wishlist
|
soliloque |
Bug Description
After scaning 18 color pages, i selected save to PNG, and i realize that Simple Scan only uses one core to do all the processing.
This might be appropriate for PDF saving, but saving PNGs is parallelizable. So you might consider using two or more cores simultaneously each saving one image. If the reason for not using multiple threads is that you want to avoid hogging the system you might consider changing the process priorities instead.
Things that are to be considered:
- check available memory. (Simple scan already scans into ram, so it is quite possible to get in situations where there is not enough memory to run multiple conversions at the same time )
- plan disk access (if i see this correctly SS already does the conversion in memory, so this is not a problem.)
- maybe create a possibility for the user to disable this kind of multiprocessing.
Results would be:
- most possibly this will increase saving speed 2-3-5 fold depending on system. With the appearance of low power multi-core, low clock CPU-s this is just getting more important by time.
Cons:
- If you manage the number of processes well, then almost nothing. The program will use more of the system, but most users will greatly value the faster speed of saving.
Other things for consideration:
- Obviously saving JPEGs can be done the same way.
- PDFs are a bit more tricky, but PDFs are made of of pages, which can be created and joined afterwards.
In GS it can be done like this:
$ gs -dBATCH -dNOPAUSE -q -sDEVICE=pdfwrite -sOutputFile=
Changed in simple-scan: | |
status: | New → Triaged |
importance: | Undecided → Low |
importance: | Low → Wishlist |
Changed in simple-scan: | |
assignee: | nobody → soliloque (soliloque) |
Dear Michael.
Please reconsider moving this to Wishlist. I aimed to add this as an (unarguably low priotity) performance problem.
Bests