MX -- ALEX
скорость в CACHE вполне приличная
но если прибавить - будет совсем распрекрасно

есть ли прибавка в скорости ?
или что-либо новое что позволит еще быстрее работать
============

Усовершенствование программ.

Документация 2007.1
Routine Performance Enhancements
COS routine management has been extensively revised in 2007.1. As a result, the way routines are managed by Caché is now much more efficient. The amount of overhead spent invoking a new routine may up to an order of magnitude less in this release. Furthermore, in prior releases, the number of routine buffers could become a source of contention in systems with dozens of cpus; this is far less likely.
Among the changes is the addition of a new per-process cache identifying recently used routines. The cache speeds up the process of locating routines which are used frequently within the process. In addition, the cache changes the way routine buffers are managed by the system.
In prior releases, only the actual routine buffers being executed were protected against change. All others could be modified. A consequence of this was that prior routines on the call stack could be changed (for example, by recompilation). To illustrate the issue, suppose a routine, A, was executing and then called routine, B. When B started running, A was available to be changed. If A was re-compiled while B was executing, the buffer holding A became obsolete and was released. When B attempted to return to A, Caché would notice this fact and report an <EDITED> error.
With the per-process cache in place, the <EDITED> error no longer occurs. This is because all routines on the call stack of any process have their current versions locked. So the associated buffers do not become obsolete. B always returns the proper version of its caller, A.
To carry the examination further, if B returns to A and, while A is executing, B is recompiled. The next call from A to B will execute the re-compiled version of B. Similarly, if A is re-compiled while B is executing and B then calls A, the new version of A will be invoked. When the new A returns to B and B subsequently returns, it will return to the prior version if A that was preserved in the routine buffer.
The initial size of the per-process cache (called the "routine vector") is set at system startup. The default is 256. This number can be changed via the function, $ZU(96,29,<value>). The cache can be cleared of all routines not in use with $ZU(96,31). Note that routines are cached by namespace; changing namespaces clears the cache. Changing the routine search path via $zu(39,...) also clears the cache.
Because the per-process cache causes system routine buffers to be held until they are no longer in use, it is possible for a large collection of processes to consume all available buffers. When this happens, Cache will force the reduction of each of the per-processes cache by some amount, freeing unused buffers. This reduction may recur until sufficient buffers are available for sustained operation.
Note:
By default each process may cache up to 256 routines. As the system starts running out of available buffers, it will adjust the number of cached routines allowed per process down by 10% every quarter-second. When the number of cached routines per process is 30% of the originally configured number, Caché will log a message to the console, indicating the system may no longer be running efficiently.
When the number reaches 20% of the original setting, Caché will log a warning; and at the 10% threshold will log a “severe” message to the console that indicates the system may hang.
The system will hang when it runs out of routine buffers and cannot free any for use.
Caution:
The routines held in the cache by dead processes keep the buffers they hold in use until the dead process is removed or the system shuts down.



Усовершенствования журнала

Документация 2007.1Journal Enhancements
With this release, a number of internal improvements have been made to the performance and reliability of synchronous journal writes. In addition, system management improvements have been made to enable journal files to be retained on shadow systems for a limited period of time.

Усовершенствования в SQL. Например:

Документация 2007.1Aggregate Optimizations — This release includes performance enhancements for SQL queries with multiple aggregates or with a combination of aggregates and GROUP BY.

Вадим

Странные результаты получились. Во всяком случае Cache' 5.2 быстрее Cache' 5.1. на наборе тестовых приложений в лаборатории InterSystems, которая занимается исследованиями производительности.

Еще пара комментариев
1. Почему нельзя применять new и if {} ?
2. Вы тестируете Cache' 5.2. Single User, которая ограничена по производительности. Не факт, что это влияет на этот тест, но все таки. Попробуйте лучше многопользовательскую версию.
2. Усовершенствования программ в Cache 2007.1.

Вадим