Making lots of extents was a technique that had a limited amount of usefulness 20 years ago. It worked because some operating systems had some very serious limitations that no longer exist. Even on Windows.
What your vendor should have done was to create properly configured
storage areas. That will result in more extents than a default configuration but it is very unlikely that they would all be the same size.
For more detailed ideas regarding storage areas read
this article. The article was written for Progress v9. The ideas still work with OE10 but
type 2 storage areas provide still more benefits.
You can get the information that you seek regarding utilization of your storage areas and extents by running a dbanalysis report and/or writing some custom schema/vst reports. Or you could obtain a copy of
ProTop. The GUI version is much nicer but you will need a 10.2A client to run it (the db can be any point release of v9 or OE10). ProTop has answers to those sorts of questions already built in.
Your other big problem is that you have a "workgroup" license. This license does not support most of the really useful tuning options. Worse yet prior to 10.1B there are
very serious performance issues when running a WG db on a multi-core server. The WG db uses a resource locking algorithm which assumes a single CPU -- it performs spectacularly poorly on multi-core systems (nobody anticipated the ubiquity of multi-core systems when v9 and 10.1A were still current products). There is a partial fix for the problem in 10.1B. No amount of tuning will cure this problem.