[AcCoreConsole] Disappointed with Performance

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
When doing batch processing with the AcCoreConsole, we have to launch the AcCoreConsole.exe everytime we want to process a drawing. I find that this seems slow as the overhead to spin up the process and then perform a netload is slow.
I'd rather spin up AcCoreConsole.exe once, do a netload once, and then pass it my scr which defines what to do, which would include opening the next drawing, and close.
Can we re-use the AcCoreConsole process to handle more than one drawing? Even when I parallize my process (but being sure to not launch too many threads [ideally I spin up threads to match my core count]), I don't find a huge time savings when using the old approach and spinning up acad.exe with the full GUI.
Where are the savings and benefits?!