[DiscordArchive] are you sure those are writes, and not reads?
[DiscordArchive] are you sure those are writes, and not reads?
Original source
But ideally Nox would do it since their setup can handle many, many, many more bots than mine can.
rektbyfaith
08-19-2025, 11:04 PM #21Archived author: Revision • Posted: 2025-08-19T23:04:30.312000+00:00
Original source
But ideally Nox would do it since their setup can handle many, many, many more bots than mine can.
Original source
yeah can't say, like i said I know nothing of playerbots or how it works. maybe there's some stupid quirk that it needs to save them. or it's simply a mistake idk
rektbyfaith
08-19-2025, 11:05 PM #22Archived author: Takenbacon • Posted: 2025-08-19T23:05:48.759000+00:00
Original source
yeah can't say, like i said I know nothing of playerbots or how it works. maybe there's some stupid quirk that it needs to save them. or it's simply a mistake idk
Original source
It could be a mistake, and no one questioned disk writes until recently
rektbyfaith
08-19-2025, 11:08 PM #23Archived author: Revision • Posted: 2025-08-19T23:08:09.461000+00:00
Original source
It could be a mistake, and no one questioned disk writes until recently
Original source
Maybe worth noting, I increased PlayerSaveInterval from 15 mins to 100, that did have a minor effect on disk writes, at most it was no more than 15% decreased. I would say that was a marginal error.
PB also has the setting RandomBotUpdateInterval (20 second default). Setting that to very high values had zero effect.
Also noticed, there is an obvious linearity in disk write increases, once the variable BotActiveAlone is disabled and 100% of bots are made active:
1K 100% active bots ~9MB/s
4K 100% active bots ~36MB/s (9MB/s per every 1K bots)
8K 100% active bots ~72MB/s (9MB/s per every 1K bots)
These values are sustained writes, taken about 10 mins after server start once it had time to stabilize. My guess is that maybe these are per-character state tables being updated in real-time, not the character save itself (the latter having very obvious spikes consistent with PlayerSaveInterval timing)
![[Image: Untitled.png?ex=690c251d&is=690ad39d&hm=...d7d1282fc&]](https://cdn.discordapp.com/attachments/284323424032129024/1407583311290826792/Untitled.png?ex=690c251d&is=690ad39d&hm=6010e66506f03596c6e7886268dec61909d5f9a8244d603b6b9a72ed7d1282fc&)
rektbyfaith
08-20-2025, 04:33 AM #24Archived author: Diro • Posted: 2025-08-20T04:33:33.093000+00:00
Original source
Maybe worth noting, I increased PlayerSaveInterval from 15 mins to 100, that did have a minor effect on disk writes, at most it was no more than 15% decreased. I would say that was a marginal error.
PB also has the setting RandomBotUpdateInterval (20 second default). Setting that to very high values had zero effect.
Also noticed, there is an obvious linearity in disk write increases, once the variable BotActiveAlone is disabled and 100% of bots are made active:
1K 100% active bots ~9MB/s
4K 100% active bots ~36MB/s (9MB/s per every 1K bots)
8K 100% active bots ~72MB/s (9MB/s per every 1K bots)
These values are sustained writes, taken about 10 mins after server start once it had time to stabilize. My guess is that maybe these are per-character state tables being updated in real-time, not the character save itself (the latter having very obvious spikes consistent with PlayerSaveInterval timing)
1 Guest(s)
1 Guest(s)