woggioni/rbcs
1
0
Fork 0
Code Actions Packages Releases 4 Wiki Activity

update Netty to 4.2.0
All checks were successful
CI / build (push) Successful in 17m48s
Details

Browse Source
This commit is contained in:
Walter Oggioni
2025-04-15 23:11:07 +08:00
parent ae8817ad2a
commit 3266e7a70e
11 changed files with 124 additions and 101 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docker/README.md
View File

@@ -11,11 +11,15 @@ The `memcache` image is similar to the `vanilla` image, except that it also cont
the `rbcs-server-memcache` plugin in the `plugins` folder, use this image if you don't want to use the `native`
image and want to use memcache as the cache backend
The `native` image contains a native, statically-linked executable created with GraalVM
The `native` image contains a native, statically-linked executable created with GraalVM Native Image
that has no userspace dependencies. It also embeds the memcache plugin inside the executable.
Use this image for maximum efficiency and minimal memory footprint.
## Which image shoud I use?
The `jlink` image contains a custom Java runtime created with GraalVM's Jlink
that only depends on glibc. It also contains the memcache plugin in the module path.
Use this image for best performance.
## Which image should I use?
The `native` image uses Java's SerialGC, so it's ideal for constrained environment like containers or small servers,
if you have a lot of resources and want to squeeze out the maximum throughput you should consider the
`vanilla` or `memcache` image, then choose and fine tune the garbage collector.