Raspberry Pi is raising prices on some products due to increased RAM costs. Among other things, prices for the 4GB CM4 and CM5 have gone up $5, the 8GB models cost $10 more, and the Raspberry Pi 500 costs $10 more. https://www.raspberrypi.com/news/5-10-price-increases-for-some-4gb-and-8gb-products/ #RaspberryPi #RAM
just small circles 🕊
boosted
One thing that really pisses me off personally is the #regression in terms of #Messenger#Apps.
My personal distaste and dislike for #proprietary, #SingleVendor & #SingleProvider #services like #Signal¹, #Telegram, #Discord², #WhatsApp, #Slack, #MicrosoftTeams, etc. aside:
WHY is there no #CrossProvider#Messenger to handle that shite?
WHY does everyone of these shitty providers think people want to download their #bloated#WebApp that takes up triple digit Megabytes if not entire Gigabytes and will gobble up all the #RAM and #CPU they can??
This problem ain't new and already got solved for corporate social media ages ago! (Not to mention actually good messengers!)
I mean
API 0- style access because obviously none of the platforms will allow, endorse or support such an endeavour and actively fight the developers and users !
So yeah, consider this a call for a @gajim / #Gajim or @pidgin / #Pidginfor garbage platforms!
One thing that really pisses me off personally is the #regression in terms of #Messenger#Apps.
My personal distaste and dislike for #proprietary, #SingleVendor & #SingleProvider #services like #Signal¹, #Telegram, #Discord², #WhatsApp, #Slack, #MicrosoftTeams, etc. aside:
WHY is there no #CrossProvider#Messenger to handle that shite?
WHY does everyone of these shitty providers think people want to download their #bloated#WebApp that takes up triple digit Megabytes if not entire Gigabytes and will gobble up all the #RAM and #CPU they can??
This problem ain't new and already got solved for corporate social media ages ago! (Not to mention actually good messengers!)
I mean
API 0- style access because obviously none of the platforms will allow, endorse or support such an endeavour and actively fight the developers and users !
So yeah, consider this a call for a @gajim / #Gajim or @pidgin / #Pidginfor garbage platforms!
The new LPDDR6 standard could bring support for faster memory with data rates up to 14.4 Gbps while also using less power than LPDDR5. We could see the first LPDDR6 products arrive within the next years or so. https://www.tomshardware.com/pc-components/dram/jedec-publishes-first-lpddr6-standard-new-interface-promises-double-the-effective-bandwidth-of-current-gen#JEDEC#RAM#Memory #LPDDR #LPDDR6
I just stress-tested the current dev state of #swad on #Linux. The first attempt failed miserably, got a lot of errors accepting a connection. Well, this lead to another little improvement, I added another static method to my logging interface that mimics #perror: Also print the description of the system errno. With that in place, I could see the issue was "too many open files". Checking #ulimit -n gave me 1024. Seriously? 🤯 On my #FreeBSD machine, as a regular user, it's 226755. Ok, bumped that up to 8192 and then the stress test ran through without issues.
On a side note, this also made creating new timers (using #timerfd on Linux) fail, which ultimately made swad crash. I have to redesign my timer interface so that creating a timer may explicitly fail and I can react on that, aborting whatever would need that timer.
Anyways, the same test gave somewhat acceptable results: throughput of roughly 3000 req/s, response times around 500ms. Not great, but okayish, and not directly comparable because this test ran in a #bhyve vm and the requests had to pass the virtual networking.
One major issue is still the #RAM consumption. The test left swad with a resident set of > 540 MiB. I have no idea what to do about that. 😞 The code makes heavy use of "allocated objects" (every connection object with metadata and buffers, every event handler registered, every timer, and so on), so, uses the #heap a lot, but according to #valgrind, correctly frees everything. Still the resident set just keeps growing. I guess it's the classic #fragmentation issue...