@Kurt_Bremser - the "chatty" network behavior used to be more of an issue in earlier days of EG, but the "collecting results" phase should not be too bad in modern versions of EG. However, the volume of ODS results and large numbers of output data sets can have an impact, especially over a slower network.
@Lenvdb - you might try the techniques in this blog post to turn off the default ODS output to see what happens. You can also try deleting unnecessary transient data sets at the end of your program to reduce the "checking" that EG performs to decide what data to add to the project output. As a trick, you can direct your output data to a libname that you CLEAR at the end of your program, effectively hiding them from EG. The data files still exist, but EG won't try to add them to the project since the libname isn't present.
If you decide to pursue with Tech Support, they will want you to turn on Application Logging (from Tools->Options). This will generate detailed application logs that Tech Support and R&D know how to read. You can have a look at these logs yourself and maybe glean an idea of what's slow...but the logs are not designed for a lay person to read.
