I am worried about the real max size of an Persistenty World. Where is the actual size limitation of the server? Server needs to load the hole module in memory at a time? Can run a 6gb persisten world module on a 4gb windows 32 XP server?
Max limit in gigabytes of a PW?
Débuté par
tuerceviolinesDA
, mai 09 2011 09:22
Retour en haut
#2
Posté 09 mai 2011 - 12:54
kamalpoe
-
- Members
- 711 messages
Limit is 2 gigs, but having an interesting server is more important than having 2 gigs.
#3
Posté 09 mai 2011 - 04:13
painofdungeoneternal
-
- Members
- 1 799 messages
2 gigs normally
3 gigs with some option set to allow addressing higher memory.
Higher even than that on 64 bit windows.
These are all issues with the OS and the maximum addressable memory for an application.
Technically though, if this is an issue for you, you are either one of the pre-existing massive PW's which have a huge staff and 60 players all the time, or you are doing something wrong. I would suggest volunteering on another "established" PW soas to learn how to make properly optimized areas prior to proceeding further.
3 gigs with some option set to allow addressing higher memory.
Higher even than that on 64 bit windows.
These are all issues with the OS and the maximum addressable memory for an application.
Technically though, if this is an issue for you, you are either one of the pre-existing massive PW's which have a huge staff and 60 players all the time, or you are doing something wrong. I would suggest volunteering on another "established" PW soas to learn how to make properly optimized areas prior to proceeding further.
#4
Posté 09 mai 2011 - 04:17
NWN DM
-
- Members
- 1 126 messages
Not a PW but my campaign module has over 100 areas and is only around 680 mb, so even with "only" a 2 GB limit, you should be fine.
#5
Posté 10 mai 2011 - 02:01
Sadistic Leprechaun
-
- Members
- 20 messages
My PW is over 2GB. I use a 64-bit version of Windows Server, and have 6 GB of RAM.
The main issue I have found is the initial loading. I use a few tricks:
1) I remove the TRN files. They are not needed for the module to run, just for the toolset. That is a nice chunk right there.
2) I move most files (items, critters, encounters) to the override folder. I always leave the areas and scripts in the main directory, but it speeds up loading a great deal, especially with our module - we have over 1000 custom monsters, over 2000 custom items, etc. This was bogging down the loading time greatly.
We have 150 areas, many outdoors, including some just for events. 2GB should be plenty for any PW with a few exceptions.
The main issue I have found is the initial loading. I use a few tricks:
1) I remove the TRN files. They are not needed for the module to run, just for the toolset. That is a nice chunk right there.
2) I move most files (items, critters, encounters) to the override folder. I always leave the areas and scripts in the main directory, but it speeds up loading a great deal, especially with our module - we have over 1000 custom monsters, over 2000 custom items, etc. This was bogging down the loading time greatly.
We have 150 areas, many outdoors, including some just for events. 2GB should be plenty for any PW with a few exceptions.
