I noticed that binary-content: it's single core.
Is it possibly to make it multicore, in order to process several files in parallel?
[Solved] binary-content: can be multicore?
[Solved] binary-content: can be multicore?
Last edited by w64bit on Thu May 04, 2023 11:06 am, edited 1 time in total.
Re: binary-content: can be multicore?
Everything should use multiple threads for SSDs by default.
To confirm:
To set a drive to use multiple threads:
Please note: Everything will only ever use one thread for a single file.
That is, Everything will not use multiple threads to search a single file.
Multiple threading is only used to search two or more files at the same time.
To confirm:
- In Everything 1.5, from the Tools menu, under the Debug submenu, click Statistics.
- Scroll down to the drive you are searching.
- Check the multithreaded status. (should be: Yes)
To set a drive to use multiple threads:
- In Everything 1.5, from the Tools menu, click Options.
- Click the NTFS tab on the left.
- Right click your drive.
- Under Advanced, under the Threads submenu, check Multiple threads.
- Click OK.
Please note: Everything will only ever use one thread for a single file.
That is, Everything will not use multiple threads to search a single file.
Multiple threading is only used to search two or more files at the same time.
Re: binary-content: can be multicore?
Something new for me.
I set it. All OK.
But, if I delete the value for fat/refs/ntfs/remote_volume_multithreaded or folder_multithreaded, Everything is set it to 0, which means "use default"
Is there any setting which controls "default" behaviour?
or
Is it possible to have (when undefined) fat/refs/ntfs/remote_volume_multithreaded and folder_multithreaded automatically set to 1, when max_threads>1
I set it. All OK.
But, if I delete the value for fat/refs/ntfs/remote_volume_multithreaded or folder_multithreaded, Everything is set it to 0, which means "use default"
Is there any setting which controls "default" behaviour?
or
Is it possible to have (when undefined) fat/refs/ntfs/remote_volume_multithreaded and folder_multithreaded automatically set to 1, when max_threads>1
Re: binary-content: can be multicore?
Currently, there's no setting to specify the default multithreading.
The next alpha update will have a default_multithreaded ini setting.
I'll make a post here once this is ready for testing.
The next alpha update will have a default_multithreaded ini setting.
I'll make a post here once this is ready for testing.
Re: binary-content: can be multicore?
There's currently an issue with Everything 1.5.0.1331a - Everything 1.5.0.1343a detecting SSDs.
Everything will currently never automatically enable multithreading.
I will have this fixed in the next alpha update.
I'll have an update soon.
Everything will currently never automatically enable multithreading.
I will have this fixed in the next alpha update.
I'll have an update soon.
Re: binary-content: can be multicore?
Everything 1.5.0.1344a adds a default_multithreaded ini setting to specify the default multithreading.
To set the default multithreading value (not recommended):
This version also fixes an issue with detecting drives that incur a seek penalty.
Drives that do not incur a seek penalty will default to using multiple threads.
To set the default multithreading value (not recommended):
- In Everything 1.5, from the Tools menu, click Options.
- Click the Advanced tab on the left.
- To the right of Show settings containing, search for:
default - Select default_multithreaded.
- Set the value to: Multiple threads
- Click OK.
This version also fixes an issue with detecting drives that incur a seek penalty.
Drives that do not incur a seek penalty will default to using multiple threads.