Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

i think i finally may have figured out the main problem that was going on with #realy on my VPS...

it has a memory limiting setting that was set to 1gb and idk for what reason, it seemed to stall and get stuck, yet if i turned it down to the default, 250mb, it runs much better... mysterious runtime variables... probably would even be better to not mess with them but i figured put it there to hint to the GC to try and keep the pile small and sweep it in little bursts to help performance on low spec hardware... it probably doesn't matter making that value bigger on my dev box because it has 64gb of memory and it could garbage up a lot more than it probably is, but performance is much the same

Reply to this note

Please Login to reply.

Discussion

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

yeah, verifying it, the setting was necessary to make it behave in the 2gb memory on the VPS, on my pc it doesn't do this stalling thing that it was doing on the vps

i think that may actually have been the main problem i was having with the other refactored version... because a lot of those changes now are in the realy repo so, meh, shrug, it works, carry on

i get quite agitated when my relay seems to be buggin, really makes me tense

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

nah, that didn't seem to work either... i guess i'm gonna have to do some memory and cpu profiling, fortunately i have that all ready to go as well

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

haha just as i was writing that i saw some apple mobile device using person was accessing the API on my relay on the VPS just now

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

so, looking at top on my VPS i can see that realy is using about 1gb of memory... the stalling was probably mainly because it was blowing out into swap... i might actually try dialing down its memory limit target to 100mb and see how that works

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

well, i set it to 100mb and that didn't change the amount of memory it uses

didn't seem to do anything, but setting it to 1gb was definitely causing a problem

default is 250mb anyway, seems to be about right, and in reality it uses 1gb... that's fine i guess... it does make the minimum requirement for a vps at 2gb memory tho

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

it actually now seems to be working, the memory oscillates between about 400mb and 600mb now... i found a good doc on go.dev about it and that's the expected pattern

i lowered the memory limit to 100mb and gc ratio to 20% nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj that seemed to do the trick

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

yes it is also more responsive now too

i still think i need to examine the thread handling a bit somewhere, it's difficult though because of the hybrid request/socket pattern of the nip-01 architecture

still, 600mb means a lot more space for database disk caching

Avatar
cloud fodder 8mo ago

64 gig damn, i only got 16/embarrassed

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

yeah, i had a 32gb pc back in 2018 and in 2020 it was basically stolen from me... was a great rig for doing programming... and a 24" 4k display as well, those cunts... it did have a nvidia 1080 too... i like to game sometimes and i hate shitty slowness... though for the price the rx7800xt i got isn't exactly amazing, good though, a lot of older games run at over 80fps in 4k which is nice... plus the new display is QD-OLED at 240hz, i have got quite used to having high frame rates, 60hz now is beyond painful, 75 is bearable like the cheap panel i have on the side for browsing/logwatching

Avatar
cloud fodder 8mo ago

tbf my last laptop had 32, there was a ram skimping happened in this gen

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

yeah, idk if 64 is much better than 32, maybe if the memory is faster, but i'm not upgrading for a while yet, this should be good for another couple years i reckon, then i'll get DDR5 memory, but probably not 128, i don't see the point

all it really does is make it take longer for badly written code to blow up and get OOM killed, that was a huge problem in the first attempt i made at forking khatru, and eventually fiatjaf figured out it was a bug he made, i couldn't find it so i just switched to relayer which was much better written - but i see utxo pimping his WoT relays built off it so i guess the bug got fixed but i'd already moved on

and anyway i ended up massively trimming down the relayer architecture, just tonight noticed that there was an assload of repeated code and one of the interfaces wasn't even being used anymore that it was tied to... and that was the main thing i was trying to do with my failed refactor of the last week... ironic

Avatar
semisol 8mo ago

change GOGC

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 8mo ago

yeah, it might be that