# JDE HTML Web Server JVM Sizing Calculator

> Source: https://netray.co/tools/jde-web-server-jvm-sizing-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

First-pass sizing of JDE web server JVM count from logged-in users, memory per session and heap, with an N+1 spare.

## Category

oracle

## Erp

Oracle JD Edwards EnterpriseOne

## Audience

- JDE CNC administrator
- Infrastructure architect

## Tool

**Kind:** calculator

**Inputs:**

#### Peak logged-in users

**Key:** users

**Type:** number

**Default:** 400

**Min:** 1

**Step:** 25

**Unit:** users

#### Share actively working at once

**Key:** conc

**Type:** number

**Default:** 35

**Min:** 1

**Max:** 100

**Step:** 1

**Unit:** %

#### Memory per session

**Key:** mb

**Type:** number

**Default:** 12

**Min:** 1

**Step:** 1

**Unit:** MB

**Help:** Assumed placeholder. Measure from a heap dump or monitoring under real use.

#### Heap per JVM

**Key:** heap

**Type:** number

**Default:** 8

**Min:** 1

**Step:** 1

**Unit:** GB

#### Base footprint per JVM

**Key:** base

**Type:** number

**Default:** 1.5

**Min:** 0

**Step:** 0.25

**Unit:** GB

**Help:** Application classes and caches before any user logs on.

#### Target heap utilization

**Key:** util

**Type:** slider

**Default:** 65

**Min:** 40

**Max:** 85

**Step:** 5

**Unit:** %

**Outputs:**

#### Session memory needed

**Key:** session_gb

**Expr:** users * mb / 1024

**Format:** decimal

**Description:** GB for all logged-in sessions.

#### Usable session memory per JVM

**Key:** usable

**Expr:** max(0.1, heap * util / 100 - base)

**Format:** decimal

#### JVMs needed

**Key:** jvms

**Expr:** ceil(session_gb / usable)

**Format:** integer

**Primary:** true

#### JVMs with one spare (N+1)

**Key:** jvms_spare

**Expr:** jvms + 1

**Format:** integer

**Primary:** true

#### Users working at once

**Key:** active

**Expr:** users * conc / 100

**Format:** integer

#### Active users per JVM

**Key:** active_per_jvm

**Expr:** active / jvms_spare

**Format:** decimal

**Chart:**

#### JVMs needed vs peak users

**Type:** line

**X:** users

**From:** 50

**To:** 2000

**Steps:** 40

**Series:**

- jvms

**Disclaimer:** Starting point only. Validate with load tests and your Oracle sizing guidance before buying hardware.

## Content

**Intro:** How many JVMs does the JDE web tier need? The honest answer depends on session memory, which varies by how people use the system. This calculator gives a transparent first estimate you can adjust as you gather real numbers.

**Sections:**

#### How to use it

**Body:** Count peak concurrent logged-in users, not named users. Estimate session memory from monitoring on your current servers if you have it. Enter the heap you plan per JVM and a target utilization that leaves headroom for garbage collection. The result is the JVM count and a count with one spare for failover.

#### The logic

**Body:** Total session memory is users times megabytes per session. Each JVM contributes heap times target utilization, minus its base footprint. Dividing gives the number of JVMs. A spare keeps the service up when one instance restarts or is patched.

**Bullets:**

- Smaller heaps often collect faster than huge ones.
- Active users drive CPU; sessions drive memory.
- Keep headroom for peak days such as quarter close.

#### What this does not cover

**Body:** It ignores CPU, the enterprise server, the database and network latency. A web tier can be memory-sized correctly and still be slow because logic runs on the enterprise server. Treat this as one input to a sizing exercise, not the answer.

**Cta:** Netray can help review your monitoring data and sizing assumptions with your CNC team.

**Faq:**

#### What memory per session should I use?

**Answer:** There is no universal number. It depends on applications used, grid sizes and caching. Measure on a comparable environment and update the default.

#### Why use a utilization target?

**Answer:** Running a heap near full causes long garbage collection pauses. A target such as 60 to 70 percent leaves room for spikes.

#### Does this work for cloud deployments?

**Answer:** The memory arithmetic applies, but cloud autoscaling and instance sizes change the economics. Use it to size the baseline.

#### How often should I re-run it?

**Answer:** Re-run after user growth, new modules, or a tools release upgrade that changes memory behavior.

## Search terms

jde jvm sizing, jd edwards html server sizing, jde web server memory per user, jde weblogic jvm count, jde user capacity planning, jde heap size calculator

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json