Equator Server version 3.5 has been released:

  • On disk index scan has been implemented:
  • It is now possible not to load index files of the last fusion stage in RAM.

    This enhancement allows to reduce memory usage several times with almost no query performance degradation.

  • Full scan queries became twice as fast due to block level parallelization enhancement.
  • Key parameter queries performance enhanced for up to 20% due to decompression optimization.

Read More

27 Sep, 2016


Equator Server version 3.4.3 has been released:

  • Predicates priority has been reviewed to ensure optimal query execution planning.

Read More

30 Jun, 2016


Equator Server version 3.4.2 has been released:

  • Memory leak related to JMX interface has been fixed.

Read More

14 Jun, 2016


Equator Server version 3.4.1 has been released:

  • Parallel search issue in the sharded mode has been fixed.

Read More

26 May, 2016


Equator Server version 3.4 has been released:

Read More

18 May, 2016


Equator Server version 3.3.4 has been released:

  • Subdirectories support for raw data files has been added:
  • Raw data files can now be processed from subdirictories taking into account the dates in the directory name. Files from the root directory will be processed first.

    After the processing raw data files can be moved into subdirectories preventing file system performance degradation due to many files in one directory.

Read More

25 Feb, 2016


Equator Server version 3.3.3 has been released:

  • Memory leaks during initial loading and merging file processes have been fixed.

Read More

1 Feb, 2016


Greenwich Server version 3.6.4 has been released:

  • Several odbc driver improvements:
  • In previous versions the number of simultaneously running queries never actually reached the 'query set max runnable' parameter value.

    The issue related to adding extra characters after non-ASCII rows has been fixed.

    Other minor bug fixes.

Read More

28 Jan, 2016


Equator Server version 3.3.2 has been released:

  • Minor compression bug fixes.

Read More

12 Dec, 2015


Equator Server version 3.3.1 has been released:

  • Memory leak related to inaccurate index memory storage has been fixed.

Read More

26 Nov, 2015


Equator Server version 3.3 has been released:

  • The initial loading process became more efficient and up to 45% faster.
  • Memory usage during the fusion process has been reduced for up to 60%.
  • Full scan batch queries performance has been increased for queries with a big number (several thousands or more) of non-key parameters.
  • Http interface for old data removal has been improved.
  • The new version supports JMX technology, which allows easy Equator Server monitoring.
  • Logging information became more structured and informative.
  • Http interface for old data removal has been introduced.

Read More

27 Oct, 2015


Greenwich Server version 3.6.3 has been released:

  • Several feature improvements and bug fixes.

Read More

1 Sep, 2015


Equator Server version 3.2 has been released:

Read More

30 Jul, 2015


Equator Server version 3.1 has been released:

Read More

20 Jun, 2015


The new CopperEye NoSQL data storage is now production ready.

Equator Server version 3.0 has been released:

Read More

15 May, 2015


Greenwich Server version 3.6.2 has been released:

Read More

20 Apr, 2015


Greenwich Server version 3.6.1 has been released:

Read More

03 Dec, 2014


Greenwich Server version 3.6.0 has been released:

  • Loading performance has been increased:
  • Loading performance has been increased by optimizing LoadBuffer internal logic. LoadBuffer consists of a reader that reads data from files into internal buffers and a writer that writes data from internal buffers into an index. Readers and writers operate in separate threads. Prior to the current version, the number of internal buffers was fixed and size was changeable via configuration file. In the current version number of the internal buffers is dynamic and increases automatically to achieve optimal performance.

    This enhancement increased loading performance by over 30%.

  • Index caching logic has been fully rethought and enhanced:
  • The memory consumption is now fully predictable. With IndexCacheMode set to None queries consume almost no memory. With IndexCacheMode set to Full the IndexCacheSize parameter now precisely restricts the memory usage. So taking in account the memory used for load buffers and repository cache (no more than several gigabytes) one can accurately predict overall memory used by the server.

    There is no performance degradation compared to the previous version.

  • Partition elimination logic has been improved:
  • For each column in a (compacted) partition, an index stores a range of minimum and maximum values that column contains. When searching a partition with a predicate on a particular column, the Core can quickly check if the predicate falls within the range of values held in that partition. If the predicate is outside that range, then no matching records will be found, and the partition will be skipped entirely for the search.

    This enhancement increases query performance when few records are returned and most query time is wasted on indices scanning.

  • Volume based licensing has been implemented:
  • Two license types have been added: License limited by the overall data records number. License limited by the overall data size. If one of the limitation has been exceeded an error will be returned while querying against the GreenwichServer (file indexing will not be stopped).

    The following commands have been added to the AdminClient: server [show] limits – to show limits and current value. server update limits – to update the current value. server set limits max – to increase limits by 20% and ask support about the license extension or delete old stripes.

    If the license is exhausted, there are 3 possibilities: Buy license with greater amount. Delete old stripes. Temporarily increase limits by 20%.

    Server update limits command runs automatically every 24 hours.

  • License files now support Windows CR+LF line endings.
  • The following functions have been added to the ASCIIFileReader:
    • Uppercase
    • Lowercase
    • Truncate
    • Substitute

  • The following configuration parameters have been deleted from the GreenwichServer.conf file:
    • MaxParallelQuery - performance tests show that this option is not of much practical benefit, and when set to a high value actually reduces query performance.
    • CostPartitionsNumber - became obsolete due to enhanced memory management logic.
    • IndexCacheRangeFraction, IndexCacheStrict - became obsolete due to enhanced memory management logic.
    • ServerLogging - there are no known conditions not to write the server log file.
    • LogEncoding - log files are now written in the user locale.
    • Security - there was only one option ('Internal') for this parameter.

  • The following tools have been deleted from the GreenwichServer distribution:
    • Compactor - duplicates compacting logic in server, but without modifying the repository - not useful.
    • Preloader - duplicates 'schedule preload' command in AdminClient.

  • Query log information has been improved:
  • In the older versions query sent against GreenwichServer from Oracle using odbc was logged in the .log only after the next query. Now every query run against GreenwichServer from Oracle using odbc will be logged right after the results are returned.

      The inforamtion about optimiser choice has been added to the query log.
    • 1 : OPTIMISER CHOOSING BETWEEN 2 INDEXES:
    • 1 : DATA_IDX1
    • 1 : DATA_IDX7

    The inforamtion about partition elimination using new min/max has been also added to the query log.

    Fetching from index is finished, total partitions: , skipped by min/max:

  • Query kill logic has been enhanced:
  • In the older versions a query could only be killed on the partition scanning phase using 'query kill all' command. Now it is possible to kill query on any phase using 'query kill '.

  • No such loader issue resolved:
  • It is possible to view loader information in any case. Previously there was a problem when in some conditions it was impossible to view information about a loader by its number.

  • Ability to add Schedule priority in DiscoveryClient has been added:
  • Now it is possible to set schedule priority using flag -o from DiscoveryClient.

  • Assertion failed error on the date formats with BINARY type has been resolved:
  • Assertion failed error while using user roles has been solved. Now it does not matter how many columns a user has access to.

Read More

1 Sep, 2014


Greenwich Server version 3.6.0 is now being tested

Read More

22 Aug, 2014


Greenwich Server version 3.5.8 has been released:

  • Fixed issue with Greenwich crashing when 'where' clause is used in queries against Greenwich system tables made via QueryClient.
  • Issue with deleting old index partitions while querying against them has been finally fixed:
  • In the previous versions of GreenwichServer, if a partition gets deleted by the DefaultMaxStripeAge job while there is a query being executed against that partition, the query would fail and the user would receive an error. The new version will allow the query to finish and a message will be logged into GreenwichServer.log.

Read More

30 Jul, 2014


Greenwich Server version 3.5.7 has been released:

  • GreenwichServer memory consumption has been improved:
  • The GreenwichServer instance with approximately 10 partititions closed every day per index will reduce RSS memory usage 5-7% of every query type towards the previous version of GreenwichServer without degradation in query performance.

  • Known issues:
  • Using 'where' clause in queries against Greenwich system tables made via QueryClient may lead to server crash.

Read More

28 Jul, 2014


Coppereye Equator Server has been in development since early 2013 and is expected to be publicly released in the late 2014.

Read More

8 Jul, 2014


Greenwich Server version 3.5.6 has been released:

  • CostPartitionsNumber parameter has been added:
  • Every query is executed against a single index, which is selected by calculating a cost for every index in a table (costing). This parameter restricts the number of partitions to be costed for every index. Such restriction leads to the RSS memory reduction and query performance acceleration in a large GreenwichServer instance, but in rare cases can lead to wrong index selection.

    The GreenwichServer instance with approximately 10 partititions closed every day per index will reduce RSS memory usage 4 times towards the previous version of GreenwichServer without degradation in query performance.

    CostPartitionsNumber 0 means that all partitions will be costed for every index in a table. Behavior identical to the previous versions.

  • Openssl RHES6 system version 1.0.1 support
  • Issue with deleting old index partitions while querying against them has been fixed:
  • In the previous versions of GreenwichServer, if a partition gets deleted by the DefaultMaxStripeAge job while there is a query being executed against that partition, the query would fail and the user would receive an error. The new version will allow the query to finish and a message will be logged into GreenwichServer.log.

  • String to timestamp convertion for Oracle has been added:
  • Now GreenwichServer can parse a string containing date, converting it to date format.

    It is possible to query against GreenwichServer using one of the following syntax: {ts'2010-04-21 04:26:01'} or '2010-04-21 04:26:01'.

Read More

25 Jun, 2014


Greenwich Server version 3.5.5 has been released:

Read More

6 Mar, 2014


Greenwich Server version 3.5.4 has been released:

  • Index behaviour with the null index fields has been improved for both ASCII and Unicode cartridges:
  • In the older version if the index field is null, this field will be indexed in every case. In the newer version this behavior was changed to the opposite, now if the index field is null, this field will not be indexed. To achieve behavior of the older version, user should set default configuration parameter in the cartridge configuration file like the following: default "", where field_N is the field number desired to be indexed in every case. If your system has some null index fields, be sure to set default parameter.

Read More

10 Feb, 2014