是否有 Java 运行时管理员这样的角色？
有数据库管理员 (DBA) 和 Unix|Windows 系统管理员。可能很快就会出现云管理员。
有一大群“管理员”，他们的任务是管理和管理在各种堆栈上运行的大量大型系统 JVM，但老实说，我遇到的人中很少有人真正了解 JVM 是什么、监控它，仪器仪表、测量和调整。大型组织是否雇用 Windows 管理员来负责管理其 Oracle 实例？然而，世界各地的企业和公共部门都希望系统管理员能够以同样的不透明性来管理 JVM。
Java 运行时管理员是否具有有效的操作角色？
There are Database Administrators (DBA) and Unix|Windows System Administrators. There are likely soon to be Cloud Administrators.
There are hordes of "administrators" who are tasked with administering and managing numerous large-system JVMs running on/in various stacks, yet I've honestly met very few of them who have any real understanding of what a JVM is, monitoring it, instrumenting, measuring, & tuning. Do large organizations hire Windows administrators who are responsible for managing their Oracle instances? yet businesses and the public sector the world over expect system admins to manage JVMs with the same opacity.
Is there a valid operational role of a Java Runtime Administrator?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
嗯..有一个应用程序服务器管理员（weblogic、websphere、jbos、glassfish...）。管理JVM只是管理系统的一部分。
Well.. there is such thing as an application server administrator (weblogic, websphere, jbos, glassfish...). Managing JVM is just managing a part of the system.
J2EE 平台“正式”定义了 平台中的系统管理员角色角色：
也就是说，理论与现实之间存在差异。
The J2EE platform "officially" defines a System Administrator role in the platform roles:
That said, there are discrepancies between theory and reality.
这是一个很好的问题，真正能够正确调优 JVM 的开发人员可能数量有限。
一家大公司最好能找到能够做到这一点的人，并在团队中利用他们。如果更好地利用 JVM，通常会节省内存、处理器和硬件。
This is a good question, the number of developers who can actually tune a JVM properly are probably limited in number.
A big company would do well to find people who can do this and utilise them across teams. There would be savings in memory, processors and hardware in general if better use of JVMs was put in place.
我们确实有“操作”管理员（负责使环境“可操作”，即将程序放入预生产或生产环境中）。
要点是：仅管理 JVM 通常是不够的。操作（或“发布”）环境也由基础设施（服务器、网络、磁盘……）、要遵循的流程（首先启动什么、如何启动……）、监控、报告。
当涉及到进程（包括在 JVM 中运行的进程）时，停止它们（以允许升级，然后重新启动）的简单事实可能非常复杂：您如何知道你的所有系统确实已经停止了吗？ （您是否错过了一个仍在单独运行的孤儿进程？）
因此，当涉及到运行时环境（其中包括 JVM 的微调）时，我们的管理员通常比“操作管理员”更重要。只是“JVM 管理员”。
We do have "Operational" Administrators (in charge of making an environment "operational", i.e. putting programs into pre-production or production environment)
The point is: administrating only the JVM is often not enough. An operational (or "release") environment is also defined by the infrastructure (servers, networks, disks, ...), the processes to follow (what to start first, how to start it, ...), the monitoring, the reporting.
When it comes to processes (including the ones running in their JVM), the simple fact to stop them (to allow for an upgrade, and then a re-start) can be incredibly complicated: how do you know that all your system has indeed stopped? (did you miss one orphan process still running alone?)
So when it comes to the runtime environment (which includes the fine tuning of a JVM), the administrators we have are often more "operational admins" than just "JVM admins".