Bug 53815

Summary: FileServer synchronisation is rather crude
Product: JMeter - Now in Github Reporter: Sebb <sebb>
Component: MainAssignee: JMeter issues mailing list <issues>
Status: NEW ---    
Severity: enhancement    
Priority: P2    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   

Description Sebb 2012-09-02 12:58:19 UTC
FileServer needs to be synchronised to provide thread-safety.

However, the synchronisation is applied at instance level.
This is unnecessary for at least part of the time.

The files Map is mostly read, not written, so could be protected using read/write locks. A Concurrent Map would not be sufficient here, as the updates need exclusive access.

Access to a single FileEntry instance would still need to be single-threaded to prevent problems when sharing a file across multiple threads.

Making such changes should improve performance by reducing lock waits.
Comment 1 The ASF infrastructure team 2022-09-24 20:37:51 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2911