GT.M V6.3-001 available

[Bhaskar, KS]

V6.3-001 brings important and useful enhancements to GT.M.

GT.M provides a fast and efficient mechanism for processes to opt-in to share their database access statistics for other processes to monitor. The statistics are the same as those available to the process itself using the ZSHOW "G" command. With no impact on monitored processes, a monitoring process can rapidly identify, for example, which processes are performing the most global SETs, or which ones are encountering the most database access conflicts (GTM-6699).

MUPIP FREEZE -ONLINE freezes database writes from global buffers to the filesystem, while allowing applications to continue database updates as long as they are able to, without requiring a write to the database filesystem. During this time, journal writes continue, ensuring database recoverability. A typical use is to freeze a filesystem to take a snapshot, or break a mirror, an operation which can take seconds to over a minute. MUPIP FREEZE without the -ONLINE enhancement freezes database updates by application processes (GTM-8362).

There are multiple optimizations for performance, some applicable to all platforms, and others specific to Linux on x86_64.

Introduced as field test grade functionality in a production release, asynchronous IO is an option for databases using the BG access method. Unlike traditional database IO, which performs synchronous IO through the filesystem cache, asynchronous IO bypasses the filesystem cache. The performance characteristics of asynchronous IO are likely to be quite different from traditional sequential IO. Although asynchronous IO in theory should be more efficient than synchronous IO by eliminating the need for the UNIX file buffer cache and thereby eliminating certain filesystem locks (e.g., filesystems mounted with AIX's CIO mount option, in practice asynchronous IO is likely to emerge from the starting gate under-performing synchronous IO because of the years that synchronous IO has been the common IO model operating systems and filesystems have had used by applications. Please anticipate extensive benchmarking and tuning for your application to achieve the best performance it can with asynchronous IO. (GTM-6838).

GT.M accepts routines with <CR><LF> line terminators. FIS thanks the participants of the 2016 "Hacking GT.M" workshop for this enhancement (GTM-4283).

As always, the release bring numerous smaller enhancements, and fixes. These, and the enhancements referred to above with their change tracking numbers are discussed further in the Release Notes (http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V6.3-001_Release_Notes.html).

I would also like to take this opportunity to let you know that Friday, March 17, is my last day at FIS. Although I am leaving FIS, I am not leaving GT.M, I will remain an active member of the GT.M community, and I plan to remain in touch with the many friends I have made over the years. Please reach out to me at any time at bha...@bhaskars.com, or my Google voice number +1 (484) 873-4467.

Regards
-- Bhaskar

K.S. Bhaskar
Development Director
Fidelity Information Services, Inc.
200 Campus Drive
Collegeville, PA 19426, USA
+1 (484) 302-3174
ks.bh...@fisglobal.com
fis-gtm.com

--
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.

[Nancy Anthracite]

Keeping up with GT.M and with Rob Tweed is a challenge!

 

I hope we are not looking at the last open source release of GT.M.

 

Nancy Anthracite

--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[David Whitten]

Bhaskar,

Thank you for your years of service to GT.M and this community.

Your activities in the past (with Open Sourcing GT.M) and with WorldVistA have shaped the future we have today.

David Whitten
713-870-3834

--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+unsubscribe@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.

To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+unsubscribe@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.

To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+unsubscribe@googlegroups.com.

[maury]

Three cheers for Bhaskar.
Without his effort and persistence, there would be no open source GT.M. It's made a significant difference on a world-wide scale.

I'm looking forward to seeing your future contributions to humanity (or just simply, seeing you in the future would be fine.)

[K.S. Bhaskar]

Thanks for the kind words, all. I look forward to continuing to work with you. I may have left FIS, but I remain engaged and active with GT.M. I will be taking some vacation, though.

Regards

-- Bhaskar

--
You received this message because you are subscribed to the Google Groups "VistA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vista+unsubscribe@googlegroups.com.
To post to this group, send email to vi...@googlegroups.com.
Visit this group at https://groups.google.com/group/vista.