[DiscordArchive] Question is, whether I should expect some possible performance impacts if each player would have all
[DiscordArchive] Question is, whether I should expect some possible performance impacts if each player would have all
Original source
Question is, whether I should expect some possible performance impacts if each player would have all 55093 item appearances unlocked?
rektbyfaith
09-22-2025, 07:31 PM #1Archived author: Vel • Posted: 2025-09-22T19:31:57.974000+00:00
Original source
Question is, whether I should expect some possible performance impacts if each player would have all 55093 item appearances unlocked?
Original source
from just having them? no, not at all
rektbyfaith
09-22-2025, 07:34 PM #2Archived author: Tea • Posted: 2025-09-22T19:34:15.656000+00:00
Original source
from just having them? no, not at all
Original source
its the learning part thats perf intensive
rektbyfaith
09-22-2025, 07:34 PM #3Archived author: Tea • Posted: 2025-09-22T19:34:28.751000+00:00
Original source
its the learning part thats perf intensive
Original source
Oh, then that's fine. So if 100 players run around with 55093 item appearances added it's completely fine?... I think I can just implement something like "ingame catalogue" player can browse and search by name and by clicking on the appearance it will get added. So that way they can basically find what they like and we actually don't need to add them to them on the very beginning.
rektbyfaith
09-22-2025, 07:36 PM #4Archived author: Vel • Posted: 2025-09-22T19:36:38.438000+00:00
Original source
Oh, then that's fine. So if 100 players run around with 55093 item appearances added it's completely fine?... I think I can just implement something like "ingame catalogue" player can browse and search by name and by clicking on the appearance it will get added. So that way they can basically find what they like and we actually don't need to add them to them on the very beginning.
Original source
yeah, all its going to cause after learning is 37kb of memory use (per player) for the bitarray
rektbyfaith
09-22-2025, 07:38 PM #5Archived author: Tea • Posted: 2025-09-22T19:38:09.537000+00:00
Original source
yeah, all its going to cause after learning is 37kb of memory use (per player) for the bitarray
Original source
but that doesnt take any cpu time
rektbyfaith
09-22-2025, 07:38 PM #6Archived author: Tea • Posted: 2025-09-22T19:38:17.158000+00:00
Original source
but that doesnt take any cpu time
Original source
And where is the player X item appearance stored? If it's like a relation table I can just cram the SQL inserts there maybe?
rektbyfaith
09-22-2025, 07:39 PM #7Archived author: Vel • Posted: 2025-09-22T19:39:28.204000+00:00
Original source
And where is the player X item appearance stored? If it's like a relation table I can just cram the SQL inserts there maybe?
Original source
auth db
rektbyfaith
09-22-2025, 07:44 PM #8Archived author: Tea • Posted: 2025-09-22T19:44:10.151000+00:00
Original source
auth db
Original source
battlenet_item_appearances
rektbyfaith
09-22-2025, 07:44 PM #9Archived author: Tea • Posted: 2025-09-22T19:44:10.638000+00:00
Original source
battlenet_item_appearances
Original source
Thanks. What will happen if player has all 55K appearances added and they log in without cache etc. Or if we add them using some bulk SQL on character create. When he logs in, it should show them like `[Some item] has ben added to your appearance collection.` because I guess server has to actually deliver those packets to the player. Wouldn't this just instantly kill the client?
rektbyfaith
09-22-2025, 07:49 PM #10Archived author: Vel • Posted: 2025-09-22T19:49:41.466000+00:00
Original source
Thanks. What will happen if player has all 55K appearances added and they log in without cache etc. Or if we add them using some bulk SQL on character create. When he logs in, it should show them like `[Some item] has ben added to your appearance collection.` because I guess server has to actually deliver those packets to the player. Wouldn't this just instantly kill the client?
1 Guest(s)
1 Guest(s)