Opened 9 years ago
Closed 9 years ago
#358 closed enhancement (fixed)
Much too high memory consumption.
Reported by: | DISABLED | Owned by: | zzz |
---|---|---|---|
Priority: | minor | Milestone: | 0.8.3 |
Component: | router/general | Version: | 0.8.1 |
Keywords: | Cc: | ||
Parent Tickets: | Sensitive: | no |
Description
I2P version: 0.8.1-0
Java version: Sun Microsystems Inc. 1.6.0_22 (Java™ SE Runtime Environment
Platform: Linux amd64
Processor: uninitialized (athlon64)
Jbigi: Locally optimized native BigInteger? library loaded from the library path
Uptime: 43h
Tunnels
Exploratory: 8
Client: 33
Participating: 8
Share ratio: 0,10
Bandwidth in/out [100/100]
Total: 22,31 / 36,09KBps
No Snark, no Plugin - Robert only (5 Local Destinations):
PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
35 15 1006M *327M* 3388 S 46.0 34.9 15h22:49 java -DloggerFilenameOverride?=logs/log-router-@.txt -Dorg.mortbay.http.Version.paranoid=true -Dorg.mortbay.xml.XmlParser?.NotValidating?=true -Di2p.dir.base=/i2p/current -Djava.net.preferIPv6Addresses=false -Djava.net.preferIPv4Stack=true -Xmx128m -Djava.library.path=/i2p/current:/i2p/current/lib -classpath /i2p/current/lib/streaming.jar:/i2p/current/lib/BOB.jar:/i2p/current/lib/jbigi.jar:/i2p/current/lib/systray.jar:/i2p/current/lib/i2psnark.jar:/i2p/current/lib/standard.jar:/i2p/current/lib/mstreaming.jar:/i2p/current/lib/routerconsole.jar:/i2p/current/lib/commons-logging.jar:/i2p/current/lib/org.mortbay.jetty.jar:/i2p/current/lib/systray4j.jar:/i2p/current/lib/commons-el.jar:/i2p/current/lib/jasper-runtime.jar:/i2p/current/lib/router.jar:/i2p/current/lib/jstl.jar:/i2p/current/lib/jasper-compiler.jar:/i2p/current/lib/i2p.jar:/i2p/current/lib/i2ptunnel.jar:/i2p/current/lib/sam.jar:/i2p/current/lib/javax.servlet.jar:/i2p/current/lib/jrobin.jar:/i2p/current/lib/wrapper.jar:/i2p/current/lib/NeodatisClassIncluder.jar:/i2p/current/lib/neodatis.jar -Dwrapper.key=J5RgKY7Y6ZWCcrD7 -Dwrapper.port=32000 -Dwrapper.version=3.1.1 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp? net.i2p.router.Router
30 10 780M *71580* 5496 R 18.0 7.5 4h49:13 Robert
35 15 14264 228 184 S 0.0 0.0 2:11.78 /i2p/current/i2psvc
—tramp
Subtickets
Change History (3)
comment:1 Changed 9 years ago by
Component: | other → router/general |
---|---|
Milestone: | → 0.8.3 |
Owner: | set to zzz |
Priority: | major → minor |
Status: | new → accepted |
comment:2 Changed 9 years ago by
I can't find the web page now, I think I saw it on a Sun Java blog a couple years back, that even the RES number vastly overstates the real amount of memory used, as Java mmaps the jar files. The gist of the post was that it's more or a perception issue. At least that's what I remember…
comment:3 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Type: | defect → enhancement |
There are some improvements in 0.8.3 as noted above, although they may not be noticable. Memory improvement is an ongoing project, not really a bug. Closing this ticket.
Sure, we can do better, and we improve things every release. More coming in 0.8.3. In particular, that release will do more scaling of the number of threads and the size of buffers, based on the max memory and bandwidth settings.
But all we can control is the heap, not the rest is the JVM.
To some extent, Java will use as much as you allow it to, you can lower the max memory setting in wrapper.config, if 128 MB is too much for you.