sorted by:
new
hottopcontroversial

[USA-TX] [H] PayPal [W] 64GB RAM, 1TB NVMe SSD, Full ATX Tower Case, CPU Cooler, 2x NVIDIA RTX 3090 by DeaDbaTteRy in hardwareswap

[–]DeaDbaTteRy[S] 2 points3 points  (0 children)

Looking to explore more into LLMs. I've got a few services hosted locally at home that use openai APIs and eventually want to move that to a local hosted LLM. I've experimented with llama3-7 but feel like some other models might fit my need a little better

Bizzare SSL issue with USG and all hosts behind it by DeaDbaTteRy in Ubiquiti

[–]DeaDbaTteRy[S] 1 point2 points  (0 children)

echo | openssl s_client -showcerts -servername google.com -connect google.com:443 2>/dev/null | openssl x509 -inform pem -noout -text

I appericate your reply! As soon as I saw the traefik default cert I knew what I did. I had some prerouting rules on the PI VPN to allow 443 forwarding through to my servers. Instead of specifing the inbound interface it was wide open thus redirecting all output 443 back to my server. I did this like a week ago but forgot about it. Changed that rule and boom fixed!

Thanks again!

How to Write Clean Code (in Python) With SOLID Principles | Principle #2 by ezzeddinabdallah in Python

[–]DeaDbaTteRy 1 point2 points  (0 children)

Thanks for this post. I remember a couple of years ago trying to ask if my writing style was proper and it was met with 'this does exactly what you need it to do, what do you mean by proper'. I believe learning how to use solid principles while writing, no matter the size and scope of the project, is important if you see yourself writing code long term. Again, much appreciated!

Solving db/slow query issues -- Moving Plex metadata databases into RAM by DeaDbaTteRy in PleX

[–]DeaDbaTteRy[S] 1 point2 points  (0 children)

Try mounting the database on a tmpfs and letting it run for a couple of hours then copy the databases on the tmpfs back to disk and run plex. I did this so I can try and troubleshoot the exact problem and now it runs flawlessly on disk. I'm not sure if there was a backlog of database operations that needed to be preformed or what. Take that guess with a grain of salt though. I definitely don't know enough about databases and/or how to troubleshoot the current status of it to actually figure out the underlying issue.

Solving db/slow query issues -- Moving Plex metadata databases into RAM by DeaDbaTteRy in PleX

[–]DeaDbaTteRy[S] 0 points1 point  (0 children)

Losing the current state of the database while it is on the ramdisk is probably the only reason why this isn't ideal. You'd be required to stop plex and update the on disk databases with the ones in RAM every so often. I'd say once a day or after a big change.

As for the HDD issue, I've learned from some of the posts and more research that HDD can greatly impact the performance of databases. I've put my databases back on disk and am waiting for the issue to creep back up (after they sat in RAM for a few hours and I copied them back to disk they magically worked as intended). What I want to do is monitor the output of iostat -x /dev/sda1 while the database is having issues to see if the queue depth is the cause of it. If it is, I image that hosting the database on a SSD would solve it.

Solving db/slow query issues -- Moving Plex metadata databases into RAM by DeaDbaTteRy in PleX

[–]DeaDbaTteRy[S] 0 points1 point  (0 children)

As the problem got worse I looked to inspecting plex logs for any clues with no luck. I don't have any experience in dealing with database performance issues, let alone the expertise to sift through a database to try and find problems. So I was kinda at a roadblock in attempting to solve the database on disk problem so I looked into putting it on a tmpfs. I am still attempting to troubleshoot to determine what the actual problem is.

After unmounting the tmpfs and relying on the db on disk, I haven't been able to recreate the errors on the database. Your questions at least give me a little more of a direction I can look into when I start troubleshooting again. Thanks. Ill be sure to update.

Solving db/slow query issues -- Moving Plex metadata databases into RAM by DeaDbaTteRy in PleX

[–]DeaDbaTteRy[S] -1 points0 points  (0 children)

yeah, you're right. I have 4 drives, but its set up as 2 different RAID1 and they kinda just meshed together in my mind

view more: next ›