Open Palworld 1.0 private server upgrade checklist: backup, server shutdown, verification and rollback and complete the actual tasks behind this question.
Related entrances
FAQ detail
What should I do if the memory keeps rising after the server has been launched for a long time?
Monitor, back up, and eliminate Mods first, and then make a restart strategy.
Classification
server
The job of the FAQ is to answer questions directly and then direct players to tools, cheat cards, or information pages that can complete the task.
30 words direct answer
Monitor, back up, and eliminate Mods first, and then make a restart strategy.
Detailed description
The increase in memory after a long run may be related to the number of bases, the number of visible Pals, building density, player online, Mod or server version, and cannot be directly attributed to a single configuration. Server owners should first keep logs and monitoring data, test based on bare server/Modded (modded) layers, set regular restart windows, and confirm that normal archiving and re-login can be achieved before and after each restart. If the server is repaired or new problems are introduced after 1.0, this question will be written back according to T0-05 server verification.
Judge your situation first
| what do you want to do now | Judgment method | Next step |
|---|---|---|
| short spike | First check whether players' entry and exit, teleportation, base loading, and large-scale battles cause spikes. Don't rush to upgrade the configuration. | Look at performance risks |
| monotonic rise for a long time | Record memory curves, logs and the number of people online, schedule regular restarts and retain archives before restarts. | See verification checklist |
| Modded server | Reappear on the naked server first, and then restore the Mod one by one; opening it all at once is of no troubleshooting value. | See Mod Catalog |
Operation sequence
| order | action |
|---|---|
| 1 | Turn on monitoring: record memory, number of people online, number of bases, logs and restart time. |
| 2 | Test the naked server baseline once to confirm whether it can be reproduced without installing the Mod. |
| 3 | Check for base density, visible pal count, path stuck, and large number of lights/particles. |
| 4 | Formulate a restart window: save before restarting, log in and out after restarting and re-enter for acceptance. |
Common misunderstandings
| Misunderstanding | why to avoid |
|---|---|
| Only upgrade configuration | If the problem is from a mod, base structure, or server version, upgrading will only delay the breakpoint. |
| Draw conclusions without monitoring | Without a timeline, it's impossible to distinguish between leaks, spikes, and normal caches. |
| Restart without acceptance | Failure to confirm saving and logging in after restarting may just postpone the problem to the player. |
Related entrances
Open Palworld Server Zone: 1.0 Upgrade, Configuration and Mod Risks and complete the actual tasks behind this question.
Related entrances
Open the Palworld Mod Directory: 1.0 Compatibility, Manager and Server Tools and complete the actual task behind this question.
Related entrances
Data status
| Project | Status |
|---|---|
| answer type | Search undertaking and task offloading, not an isolated strategy page. |
| version status | Please refer to the corner mark of the corresponding function page. |
| data boundaries | Contents that have not been published, tested or stored in the database will not be written in advance and a final conclusion will not be drawn. |
Page boundaries
This answer only accepts search intent; content that can be calculated, tracked, and requires version verification must be returned to the corresponding function page. 1.0 Unpublished or untested data will not be finalized in advance in the FAQ.
Applicable versionP1 route contract / P2 v2.0 content layer
Updated
SourceP1 A4 route contract / P2 v2.0 FAQ diversion / FAQ search intent card
UpstreamConOps current focus: Palworld P2 content-layer rebuild