[sorry for the top post, Outlook doesn't do proper quoting]
Hi Andreas,
I uploaded the latest version of GT.M that we released yesterday. I tagged the 
version as unstable. Let me know if that was the correct thing to do.

As always, thanks for help.

Amul

________________________________
From: Bhaskar, KS
Sent: Monday, June 08, 2015 1:48 PM
To: Omar Shboul; Khamis Siksek; Ahmad Sharaf; Mohammed Sharaf; Murat Khemesh; 
Wasim Naffar
Cc: FIS MLN GG GT.M Support
Subject: GT.M V6.2-002 available


V6.2-002 brings a number of modest enhancements to GT.M.

Improving performance:

  *   By reducing the number of dirty global buffers to be flushed in 
anticipation of an impending epoch, epoch tapers aim to ameliorate spikes in 
response time that can occur at epochs.

  *   $ORDER(gvn,-1) - "reverse dollar order" - of global variables is faster.

  *   Under conditions of high contention, processes holding locks exit faster, 
processes acquire database critical sections more efficiently when the mutex 
queue slots are all used, and lock acquisition is more efficient with 
substantially reduced impact on database throughput.

  *   Code size reduction that also improves performance.

Enhancements include:

  *   Intrinsic special variables: $ZUT provides a universal (across systems 
and across time zones) time stamp, and $ZHOROLOG extends $HOROLOG with 
additional pieces that provide microsecond resolution and time zone information.

  *   TLS for SOCKET devices benefits from enhancements to WRITE /TLS and 
$ZSOCKET().

  *   The environment variable gtm_autorelink_ctlmax provides a control to set 
the number of unique routine names in relink conrol files.

VIEW "POOLLIMIT" functionality introduced as field test grade functionality in 
the production release V6.2-001 is considered production grade functionality in 
V6.2-002.

As always, the release bring numerous smaller enhancements, including to the 
$ZQGBLMOD() function, better handling of split $PRINCIPAL, more helpful 
TPRESTART messages, and more. Robustness is improved, especially in the 
triggers, and security has been tightened by dropping support for dubious edge 
cases . These changes are described in the Release Notes 
(http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V6.2-002_Release_Notes.html).

Please do upgrade to V6.2-002, and tell us how it works for you.  Thank you for 
using GT.M.

Regards
-- Bhaskar

--
GT.M - Rock solid. Lightning fast. Secure. Pick any three.

_____________
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.

Reply via email to