Uneeded nodes not being removed

[confuser]

We've noticed as the pex file gets bigger and bigger it causes lag on our dedicated server. Surely it would be better to remove these empty nodes?

player1:
worlds:
Vareide1-1: {}
player2: {}
player3:
worlds:
Vareide1-1: {}
Spare: {}

I've had to write a plugin which cleans them up, our pex file went from about 30,000 lines to 5,000 and lag completely disappeared. I assume it causes lag because each time it re-does the cache it goes through each node?

[Fate-Kun]

would you kindly share that plugin with me? I have similar issues DX

[t3hk0d3]

as the pex file gets bigger and bigger

and then you have to migrate on mysql :)

[confuser]

Will the MySQL backend suffer from an equivalent of empty nodes to empty rows in the table? Surely it would be better to optimise the default file based backend to remove nodes such as the ones I've posted?

[bacon-avenger]

There is also this:

pex users cleanup [threshold]
Remove "dead" users from the file. [threshold] is in days and defaults to 30

Also, if I'm not mistaken, the createUserRecords: false setting in the PEX config will stop it from creating players in the permissions file that are in the default group and do not have anything assigned to them, such as a specific permission or prefix, at a player level.

[zml2008]

This issue is no longer relevant with the upcoming PermissionsEx 2.0. See this forum post for more information.