we are aiming at releasing version 2.1 at March 2, in time for the second phase of the Kenya roll-out.
The overall theme will be improvements to application performance and behavior in high concurrency environments. More specifically:
Report table is materialized in memory only to avoid shared resources such as physical database tables which leads to huge performance benefits.
GIS module can save map views of system and user-type, which means that a database can be bootstrapped with sensible system views while still allowing users to add their own.
Excel pivot table client tool which downloads data to a locally stored cache, this will take load off the central server.
we are aiming at releasing version 2.1 at March 2, in time for the second phase of the Kenya roll-out.
The overall theme will be improvements to application performance and behavior in high concurrency environments. More specifically:
Report table is materialized in memory only to avoid shared resources such as physical database tables which leads to huge performance benefits.
GIS module can save map views of system and user-type, which means that a database can be bootstrapped with sensible system views while still allowing users to add their own.
Excel pivot table client tool which downloads data to a locally stored cache, this will take load off the central server.
we are aiming at releasing version 2.1 at March 2, in time for the second phase of the Kenya roll-out.
The overall theme will be improvements to application performance and behavior in high concurrency environments. More specifically:
Report table is materialized in memory only to avoid shared resources such as physical database tables which leads to huge performance benefits.
GIS module can save map views of system and user-type, which means that a database can be bootstrapped with sensible system views while still allowing users to add their own.
Excel pivot table client tool which downloads data to a locally stored cache, this will take load off the central server.