Is there some practical way to limit file opens inside a mount.cifs to avoid problems on the Windows side?

I need to do frequent builds on a Linux system of a massive codebase with all source code on a Windows share.

I use a build tool that runs many compilers in parallel (The Linux system has two 6-core CPUs hyperthreaded, so running 24 way parallel compiles is faster than running fewer. But at the start of each major block of compiles, several opens of .h files fail.

I'm not 100% certain, but pretty sure the Windows system limits the number of file open requests it will queue. So if a burst of open requests happens at once (more requests coming in before the last finished opening) it fails the requests.

Once 24 worker threads are busy compiling on the Linux side, new compiles start out of sync and all the file opens succeed. But at the start and at a few choke points in the build process, 24 compiles start at once and all of them are opening include files at the same moment and several file opens fail.

Inside the cifs code on the Linux side the number of outstanding requests to Windows side must be known (how many requests have been sent but not yet replied to). Is there a way to limit the number of outstanding requests: delay sending the next request until some previous request has been answered?

Or any other suggestions?

As things stand, it is faster to run the whole build 24 way parallel with a few parts failing, then rerun to redo just the parts that failed, as compared to running less parallel to begin with. But it would be better to get 24 way parallel to work right from the start.

what MS OS are you running that is holding the data, and why has the data not been moved to a Linux NFS server?

Is this Windows server, user, also seeing some dev libraries have limits. What I'm seeing Windows early on had an limit or 512 open files, but current windows server the number is 16,383. I wonder it instead of a number of open files its from trying to open so many files its creating a I/O bottleneck causing file open's to time out.

Windows 7 Desktop system.

I have some pretty good reasons to keep the codebase on the Windows system. But I would prefer not to discuss that aspect.

I was really hoping for some way to limit the Linux side from queuing up too many requests at once.

I don't really understand the failure, but I don't think it relates to the number of files open at the same time. It seems to relate to the number of files for which open has been requested, but are not yet open.

I suspect there is an anti-virus aspect to the problem. I am required to have really vicious anti-virus software running and that causes most aspects of the Windows file I/O to be single threaded and quite slow.

win7 what vs. again please be specific. the issue could be win7 if it is less then pro you are fubar and there will be nothing you can do. if it is win7 pro or ultimate, you might be able to manipulate something on the win7 box.

if you have AV that is blocking access to files, nothing you can do other then adjust/exclude those files from your AV for these types of processes. again you are best off running/sharing Linux files via a Linux server, not a hodge podge broken OK like Microsoft.