[BETA] Release version v0.2.1 evolved to 0.2.1.0009! #14
zhenrong-wang
announced in
Announcements
Replies: 1 comment
-
It turns out that for AWS EC2 instance, if the CPU option specified (aka. hyperthreading), it needs to rebuild the instance when changing its configuration. Considering avoid the hyperthreading option. Please stay tuned for next minor version. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is a major evolution of Version 0.2.1.0007.
Main changes:
1. Added 2 important command keywords to control the running of tf.
--dbg-devel DEBUG_INFO_LEVEL
.With this option, you can specify the verbosity of tf debug log.
Options (from most verbose to least verbose): trace, debug, info, warn, err, off
--max-time MAXIMUM_WAIT_TIME
.With this option, you can define the maximum wait time for tf execution. You can specify a number in the range 600 ~ 1200
2. Now you can view the tf debug log with the
hpcopr viewlog
command.Command reference:
hpcopr viewlog -b --log dbg
3. Updated the now-server module with the recently-introduced batch mode.
Please run the server by
./my-server.ext --client-io PORT_NUMBER
. Then the server will be standby to accept requests on the specified port number. If no port number specified, the server will use default port #19885.4. Fixed known bugs.
Please check the source codes and the packages attached.
We also added a CONTRIBUTING.md to this project, looking forward to your feedback and contributions!
HPC-NOW: Start your HPC journey in the cloud now.
This discussion was created from the release [BETA] Release version v0.2.1 evolved to 0.2.1.0009!.
Beta Was this translation helpful? Give feedback.
All reactions