BLOGS

12.1

warning: file_get_contents(http://www.telize.com/geoip/107.22.126.144) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /var/www/www.4d.com/docs/includes/common.inc(1762) : eval()'d code on line 4.

Scalability in 4D Server v12 64-bit

Scalability: 510 users and the 64-bit version of 4D Server v12

To demonstrate scalability at full load, we compared the two versions of 4D Server 12.1, 32- and 64-bit, connecting 510 clients. Each client executed queries/creations/deletions in two different processes. Statistics were collected during those operations.

 

Queries under 4D Server v12 64-bit

Increasing cache size to speed up queries

Usually, scalability is not about speed. Being able to allocate more memory does not mean that an application will run faster, but that it will support a heavier load. However, there are situations where an operation will run faster just because 4D Server could use more RAM. A typical example is the cache size. The 32-bit version can allocate a maximum 2.3 GB of cache. (The remainder is used for the engine: handling connections, processes, users, code, etc.) There are no limits with the 64-bit version, which means it is now possible to fill the cache with all the data (and indexes).

Sequential sorting under 64-bit

The 64-bit environment and its benefits for sequential sorting

To demonstrate scalability's effect on performance, we compared the time it takes to perform a sequential sort using the 32- and then the 64-bit versions of 4D Server v12. A sort needs memory to store the temporary data used in comparisons. 4D Server does not use the cache for this kind of operation; it allocates the memory in the “engine memory” (any part of the virtual memory 4D Server can allocate outside the cache). We set the size of the cache to the same value in both environments.

SVG Area

Taking advantage of 4D's powerful integrated SVG capabilities, the SVG Area component brings a manipulable SVG field to your user interfaces.

The SVG Area field allows you to create vector graphics, whether hand-drawn or programmatically generated, connected to data in the host application. It supports shapes, colors and standard 4D fill patterns, and can also contain bitmap images in the form of links. The area's contents can be stored in a record or exported as an SVG file.