Opened 4 months ago

Closed 4 months ago

#2561 closed defect (wontfix)

Increase wrapper.java.maxmemory by default

Reported by: anonymous maybe Owned by:
Priority: minor Milestone: undecided
Component: router/general Version: 0.9.41
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

This error always going to happen when installing fresh I2P with high internet speed. Better to increase rams to 500MB or so (whos using less than 500mb rams or even 1GB nowadays?)

  • I2P Version and Running Environment
 I2P version:	0.9.41-0-1~disco+1
Java version:	Debian 11.0.3 (OpenJDK Runtime Environment 11.0.3+7-post-Debian-5)
Wrapper version:	3.5.30
Server version:	9.4.15.v20190215
Servlet version:	Jasper JSP 2.3 Engine
JSTL version:	standard-taglib 1.2.5
Platform:	Linux amd64 4.19.43-1.pvops.qubes.x86_64
Processor:	Haswell Core i3/i5/i7 model 60 (coreihwl)
JBigI status:	Locally optimized library libjbigi-linux-coreihwl_64.so loaded from file
GMP version:	6.1.2
JBigI version:	4
JCpuId version:	3
Encoding:	UTF-8
Charset:	UTF-8
Built By:	Undefined
  • Router Logs
7/4/19, 9:27:17 PM WARN [impleAppMain] .tunnel.BloomFilterIVValidator: Configured for 1.29MiBps share bandwidth but only 123.75MiB available memory. Recommend increasing wrapper.java.maxmemory in /etc/i2p/wrapper.config to at least 140 (MB) if the actual share bandwidth exceeds 512.00KiBps.

  • Service (Wrapper) Logs
2019/07/04 21:27:15 | Launching a JVM...
2019/07/04 21:27:15 | WrapperManager: Initializing...
2019/07/04 21:27:16 | Starting I2P 0.9.41-0-1~disco+1
2019/07/04 21:27:16 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2019/07/04 21:27:16 | INFO: Locally optimized library libjbigi-linux-coreihwl_64.so loaded from file
2019/07/04 21:27:16 | WARN: Configured for 1.29MiBps share bandwidth but only 123.75MiB available memory. Recommend increasing wrapper.java.maxmemory in /etc/i2p/wrapper.config to at least 140 (MB) if the actual share bandwidth exceeds 512.00KiBps.

Subtickets

Change History (3)

comment:1 Changed 4 months ago by jogger

This goes into the wrong direction. A router with 192M can run any size traffic. I never use more than 256M with a couple of webapps.

The cited message is issued before the router is working in full, esp. before dozens of snark threads are created. Thus it can only give a misleading indication.

When modifying wrapper, for a quick fix it would be better to include "Xss=96k". Should save around 64M currently totally wasted which could be subtracted before doing the above calculation.

comment:2 Changed 4 months ago by anonymous maybe

if thats help fixing the issue without adding more issues then its better to be add up.

comment:3 Changed 4 months ago by zzz

Resolution: wontfix
Status: newclosed

We just increased the default recently, from 128 to 256 in 0.9.38 for new installs. We can't update wrapper.config in the update.
The config is for the JVM heap which is way less than the total memory used. And just because you have RAM doesn't mean i2p should use all of it.
The message is from the bloom filter subsystem, as if you really have high bandwidth then it helps to have a big enough bloom filter.
Yes custom options like Xss may be helpful but we can't add anything like that by default because we don't know what JVM is being used and some unknown options cause the JVM not to start.
I think 256 is good for now.

Note: See TracTickets for help on using tickets.