Sounds like your issue is resolved but thought I'd respond to your question as best I can anyway. We're pretty small so we aren't doing as much as others do with TX.....Keep in mind that we limit TX to mapping data to/from corporate friendly data formats. Simply middleware. passing information to stored procedures, mainframe and populating DB tables.....
We started having problems executing certain APIs. Things ran fine on our new server for 6 months. Then, we started having problems with maps that executed FTPs, UnZips etc.... but only when the files exceded a certain size. Something over 300mb. The error messages indicated lack of resources. We started tracking them.... No unexpected spikes in CPU, Memory or disk usage.
Also, we'd always handled files that size and larger on the old server which ran 6.0 thru 6.7.1. The old box was 1.2 ghz with 2gb memory and 200GB dedicated disk. The new box is 3.nGHZ with 4GB mem and 40gb of dedicated disk (moved archiving to our NAS).
Now, we don't process 10000 transactions/files per day like you do. But, we do use one, 1 cpu Windows box to process all inbound enrollment, electronic claims, 27X real + batch queries/responses; out bound 835, enrollment, payment files; Commerce Manager, etc..... DSTX is leveraging DB, http, ftp, zips, emails and so on....
Anyway, we probably only average 1.5gb of TX input per day. Inbound eligbility files average 15-20mb(the range from 300kb to 70mb with occational 200+mb file). 300-500 http transactions daily.....
Our box rarely excedes 50% CPU/memory for more than a few minutes and was very low, below 15%, when our 'out of resource errors' occurred.
We ran the SDK's rebind option against the TX dlls in the TX root directory and the errors stopped. Can now handle files in excess of 1gb without issue. Haven't tested beyond that as realistically 300mb is about as large as our input files get and at that its maybe once every 6 months.
Someone smarter than me can explain how it works. I think it assigns specific memory addresses to dlls in the TX directory. Our nework Services area said there's a potential down side to having run the rebind and the MS articls I read on rebinding left me thinking we might be waisting our time but.... so far so good.
blah blah blah....