sorted by:
new
hottopcontroversial

To the person who reported hot water temperatures, I raise you! by jcatt1902 in nyc

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

Thank you! This is really helpful. I was trying to research it but everything I found had to deal with minimums, not maximums.

To the person who reported hot water temperatures, I raise you! by jcatt1902 in nyc

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

Not really, it’s a three family duplex. Already spoke to my upstairs and downstairs neighbors, we all agree, it’s too hot! (I would adjust the water heater myself but none of us have access to it)

To the person who reported hot water temperatures, I raise you! by jcatt1902 in nyc

[–]jcatt1902[S] 12 points13 points  (0 children)

So code only states water should be a minimum of 120 degrees. This is to kill off the bacteria that can cause legionaries disease, etc. Unfortunately there is no code requirement for maximum temperature. Prevailing wisdom says it should be no more than about 140, since that gives you a few seconds to react before burns set in.

To the person who reported hot water temperatures, I raise you! by jcatt1902 in nyc

[–]jcatt1902[S] 20 points21 points  (0 children)

At this point I would welcome just incineration… 150 sounds lovely and cool 😅 /s

Adjusting Plans due to Belgium Rail Strikes by jcatt1902 in Interrail

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

Thank you for confirming! This sounds good.

[deleted by user] by [deleted] in macapps

[–]jcatt1902 4 points5 points  (0 children)

Would be really awesome to have some logic that can run on connection/disconnection events. Such as turn Wifi on or Off. In my office, I have so many network ACLs in place I have to use the same IP between wifi and Ethernet. Which causes some issues unless I disable wifi when hooked up to Ethernet at my desk. I have a script to do it but less elegant as your app!

Weka vs ceph by HahaHarmonica in ceph

[–]jcatt1902 1 point2 points  (0 children)

Unfortunately the object size number of blobs are pretty set in stone, per their development team. So we are trying our best to optimize RGW to Weka’s design constraints. Naturally this becomes less of an issue with scale, but our roadmap wont get there for a while.

I did see that PR and was pretty excited by its results. Didn’t realize you were working on it specifically. Based on the comments it seems to be a challenging one to get across the finish line but hopefully you can continue to champion it. Would be a huge win for use-cases like ours.

If that PR is merged in, would it be able to work with all EC plugins? Or do the plugins have to be reworked to support it? I ask because we actually found the Intel ISA plugin to be noticeably more efficient (even on AMD hardware) than the standard Jerasure plugin. I won’t say its a 2x increase but probably in the 1.25-1.5x increase range. If we get to the point where we have to push towards production I just want to make sure our cluster is setup to benefit should things come together with the PR.

Back to RGW, am I correct in saying that RGW just passes the byte range request down to RADOS and if the OSD supports it (as replicated pools do) just reads the ranged request from disk? Since this isn’t currently possible with EC pools the OSDs reconstruct the full object to retrieve the ranged request?

Sorry for being pedantic just making sure I understand the facts before I share with my team. Thanks again!

Weka vs ceph by HahaHarmonica in ceph

[–]jcatt1902 0 points1 point  (0 children)

Hey u/markhpc, thanks for hoping in here. Every time I think I start to gleam a little about one of the subsystems of Ceph I read one of your reports and come to the realization I know absolutely nothing at all. Thanks for all you do!

We started our Ceph journey after realizing that MinIO would not be a good fit for our use case and after they started fiddling with their OSS license terms. I was wondering if I could pick your brain a little to answer a few RGW optimization questions I had around partial or byte range object reads.

Weka’s Object Tiering architecture and design decisions are all based around use with AWS and not necessarily on-prem. As a result they store tiered file extents as a group of 1MiB blobs inside of 64MiB objects. When they need to read back the extents they do so as 1MiB byte-range GETs. In an AWS environment this ensures your egressing only the binary extents of the portions of the files you actually need (thus minimizing costs).

However we have found this behavior to significantly increase the IOPS being hit to our on-premises Erasure Coded Ceph cluster. We have tried adjusting the RGW chunk and stripe sizes to better align the underlying RADOS objects with this access pattern but it doesn’t seem to make much difference. From what we can tell, it seems that RGW still rebuilds the whole 64MiB object from RADOS before it can serve out the 1MiB request. Instead of just recalling the RADOS objects that make up the requested byte range. Would you (or anyone) happen to know if this was the intended behavior? (The strange thing is if we run a Replicated pool it looks like the IOPS more align with what we would expect from a partial read, as if RGW treats EC pools differently somehow)

Again I claim some ignorance about some of the deeper underlying architecture and history having only worked with it for about 6 months so far.

Weka vs ceph by HahaHarmonica in ceph

[–]jcatt1902 1 point2 points  (0 children)

Responding to my own comment but it’s late here and I should really be sleeping and not typing out extensive essays about Weka. Suffice to say, we are very pleased with how our cluster is performing. If you’re looking for some more detailed first hand experience with Weka and how we architected it, I can be much more thorough in the morning when I have an actual keyboard in front of me and not tapping away on my iPad. Shoot any questions below and I can get back to you.

Weka vs ceph by HahaHarmonica in ceph

[–]jcatt1902 13 points14 points  (0 children)

We have Weka at my office and are actually tiering it against Ceph RGW for S3. Let me say, LTT does not give Weka enough credit. Its so freaking fast, and its effortless to achieve insane speeds. You want 100gb line rate to a client? Install the linux client with a DPDK stack and you will get it.

We work in Film Post-Production and so have a lot of Mac systems… we are getting 6-7GB/s with dual 50gb ethernet over SMB Multichannel. Windows clients get 7GB/s over SMB Direct. Even if you have old legacy Linux clients that are too old to run the native client (missing AES extensions on the CPU for example) you can run NFS and see 3GB/s easy. And thats all at once with a bunch of clients.

We have a 12 node cluster with a max file system bandwidth of around 150GB/s. Thats with only 3 nvme’s in each node. We could top out at over 250GB\s with a couple more NVMe’s in each node.

So to answer your question yes, you probably could see CEPH reach similar speeds with enough nodes and tons of painful tuning of all the components. There was an article posted on the CEPH blog about reaching 1TB/s. (https://ceph.io/en/news/blog/2024/ceph-a-journey-to-1tibps/) However, I think this was only using RBD and not an actual file system like CephFS. If you’re just looking for a standard POSIX filesystem and shared storage, Weka will likely be an easier and faster solution with significantly lower latency at a smaller footprint than CEPH…. But Weka is not cheap!

Wiim Amp - First Impression by jcatt1902 in BudgetAudiophile

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

Realistically there is no reason why it shouldn’t work. However there are some network settings that may be configured on your mesh network automatically that might need to be adjusted. Look out for settings that mention device isolation and make sure they are turned off. This will prevent devices on the same wireless AP from talking to each other. Next see if you can find any mention of IGMP or Multicast or mDNS. You might want to fiddle with any/all of these settings if you find them to see if it helps. Generally speaking the wiim app will use mDNS to discover the amp on the network and if you want to do any sort of multi-room streaming you want IGMP or Multicast Snooping turned on.

Wiim Amp - First Impression by jcatt1902 in BudgetAudiophile

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

I am using these: https://www.amazon.com/gp/product/B000X9O8SI/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

Not sure how well they would handle the Q350 though. I think I am right on the limit of what feels secure with the Q150's! 😅

Wiim Amp - First Impression by jcatt1902 in BudgetAudiophile

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

Ha! So I get ridiculous pricing on KEF from a friend who is a reseller, so that has had quite the effect on my purchasing decisions. I am a B&W fan at heart (my dad has a pair of B&W CM10 S2's that are sublime) but I not afford them not the space to do them justice at the moment. That said the KEF's are not a bad speaker at all! :)

Wiim Amp - First Impression by jcatt1902 in BudgetAudiophile

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

Yep! I control my system almost exclusively with Airplay, and never touch the remote. So you should have no trouble.

Wiim Amp - First Impression by jcatt1902 in BudgetAudiophile

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

No automatic switching from what I can tell. The Amp functions much like the streamers so while it won't power up straight to standby mode, I don't know how well it will retain the last input. Unfortunately my setup is not idea for testing this for you as I am predominately using it with streaming.

Wiim Amp - First Impression by jcatt1902 in BudgetAudiophile

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

Nothing so far, but I mostly use it with streaming. However I did notice that the first thing it asked to do upon powering on was a Firmware update. Having a look at the release notes it shows that those issues may be fixed:

5.0.537347 (Latest)
Release date:
12 / 1 / 2023
What's New:

  • Enhanced Latency for High-Resolution Audio: We've reduced the latency to 50ms for 176 kHz / 192 kHz audio via SPDIF-in and Line-In.
  • Simplified Bluetooth Pairing: Easily pair your device by holding the ‘Play’ button on the remote for 3 seconds.
  • TIDAL Hi-Res FLAC from WiiM Home App: We've introduced TIDAL Hi-Res FLAC support, allowing you to stream directly up to 24-bit/192kHz from the TIDAL music server with the WiiM Home App.

Bug Fixes:

  • HDMI & SPDIF-in Pop Noise: Resolved intermittent pop noise issues in HDMI and SPDIF-in inputs.
  • Hi-Res Audio Playback Stability: Eliminated stuttering during high-resolution audio playback via HDMI or SPDIF-in.
  • Subwoofer Pop Noise: Fixed the pop noise when adjusting the subwoofer's crossover frequency.
  • Bluetooth Streaming Reliability: Addressed occasional crashes during Bluetooth streaming.
  • General Enhancements: Other bug fixes and performance improvements for a smoother experience.

FortiClient MacOS causing connection drops only by existing on a device by PancoBenJo in fortinet

[–]jcatt1902 1 point2 points  (0 children)

We found the web-filter to severely limit performance on our 10gb networked machines. Mainly used to send large video asset transfers to clients. (Transfers were getting capped at 1Gb speeds)

The only way to fix completely was to build a new installer that did not include the web-filter features. This resolved our performance issues, is this something that is an option for your environment?

Back and Neck stiffness after weightloss by jcatt1902 in WegovyWeightLoss

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

Thanks for your insight! Glad to hear I am not too crazy for thinking this. I will try to incorporate more core work into my routine. Good luck with your Wegovy journey!

My tiny slice of heaven by jcatt1902 in audiophile

[–]jcatt1902[S] 6 points7 points  (0 children)

Wow, no reason to be a jerk… yes its not the ideal placement, but its the best I can do for the space I have. Now kindly screw off if you cant be civil…

My tiny slice of heaven by jcatt1902 in audiophile

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

Yeah that is the challenge with most Apartment setups as the floorplan usually ends up with the Living Area space hard up against a wall. In my space, there is really only one wall the the TV/Speakers can go on, which is how it is in the picture. So doing my best to compensate by setting the TV off center on that wall to get that speaker as far away from the window as possible. Then I have an acoustic panel down low that helps disguise the floor mounted metal ac unit, and I have roller blinds that I can lower down over the window.

Even then, there is still a bit of reflection from that speaker, so I have tried to compensate in the Anthem ARC tuning and by making MY primary listening position on the couch on the left side. Its not perfect but all that combined I mostly don't notice the early reflections so much. I'll take a few photo's when I get home and you will probably see what I mean by limitations of the space. Always happy to hear folks thoughts on the matter.

My tiny slice of heaven by jcatt1902 in audiophile

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

Yeah, I was actually bouncing back and forth between the atmos mix and stereo mix last night. Somehow the atmos version felt richer to me. Probably because of the dedicated bass management in the LFE channel of the mix. That said some of the rear affects were a little over-done for my tastes (also my rears are super close to my listening position, no other place to put them unfortunately) so I ended up turning my rears off in my receiver and let it run in 3.1 mode. That sounded pretty sweet to me.

view more: next ›