BLOGS

4D V12

warning: file_get_contents(http://www.telize.com/geoip/54.81.131.189) [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.

Fixed Bugs 4D v12.2

Thu, 2011-05-12 17:05

PHP Integration

4D v12 lets you directly execute PHP 5.3 scripts within 4D applications, thanks to our FastCGI compiled interpreter.

(You may use other interpreters, providing they are compatible. See documentation for details.)

 

Go beyond Web scripting and add real functionality to your applications.

 

You get access to a wealth of utility libraries available via PHP, providing functions such as:

  •  ciphering and hashing (MD5)
  •  handling of HTML files
  •  image handling
  •  LDAP access
  •  COM access (for Microsoft Office documents)

 

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.

Language Certification

Tue, 2010-11-30 13:54

Language Matrix

Thu, 2010-05-27 12:00

Language matrix for 4D v12.1 coming soon