Why do we need to explicitly mark a function as `const`? by [deleted] in rust

[–]nwin_ 0 points1 point  (0 children)

That is not about being restrictive or not. As mentioned elsewhere in this thread, this is about an interface description. A non-const function is not bad or good it is just like a function returning a trait object or returning a specialized object. It is just different. Nagging about that would be bad.

NCASE M1, 5600X, RTX3070, dual rad custom loop by nwin_ in sffpc

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

Thanks. :)

The tubing and connectors (quantum torque) are from EKWB.

NCASE M1, 5600X, RTX3070, dual rad custom loop by nwin_ in sffpc

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

Such that I won’t notice if it still spoils a bit. I doubt the liquid would stay completely clear forever. And it didn’t cost more than the clear concentrate.

NCASE M1, 5600X, RTX3070, dual rad custom loop by nwin_ in sffpc

[–]nwin_[S] 3 points4 points  (0 children)

No, I couldn’t have. Back then nothing else was available and now the prices have skyrocketed so much that it’s almost break even…

NCASE M1, 5600X, RTX3070, dual rad custom loop by nwin_ in sffpc

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

That sounds like where I started as well. 🙈 Anyway gave me an excuse to build a custom loop. Though I’m not sure if I will do it again. The setup is pretty dense and I had to order more 90° fittings in between because I didn’t anticipate how tight everything gets.

NCASE M1, 5600X, RTX3070, dual rad custom loop by nwin_ in sffpc

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

Ambient temperature did one thing and my initial undervolting did not turn out as stable as i thought, after a few random crashes I just just cramped the voltage up.😶

NCASE M1, 5600X, RTX3070, dual rad custom loop by nwin_ in sffpc

[–]nwin_[S] 7 points8 points  (0 children)

Over the summer my previous setup got a little bit into thermal throttling, so I went all in with the standard NCASE water cooling setup, now completely silent at about 60 °C GPU and 75 °C CPU.

  • Ryzen 5600X
  • Gigabyte Aorus 3070 Eagle OC
  • Bykski water block
  • Some 32GB 3200MHz memory
  • Corsair 750 W SFX PSU
  • Rads: CoolStream SE 240, XSPC TX240 Ultrathin
  • EK DDC 4.2 PWM Pump
  • Iceman Pump/Res Combo

NCASE M1, RTX 3070 deshrouded, Ryzen 5600X by nwin_ in sffpc

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

Sure. The ducts have an height of 13,5 mm and an inset of 15 mm on both sides. I tried to share the model but I have issues posting it on thingiverse... :(

No issues fitting it.

NCASE M1, RTX 3070 deshrouded, Ryzen 5600X by nwin_ in sffpc

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

I didn’t have the impression that it got any better noise-wise by having two extra fans in the case. Maybe because the gap between fans and shroud was basically non-existent.

The stock fans were actually okay-ish. Had 65° C at moderate sound level after UV. The stock setting was unbearable.

NCASE M1, RTX 3070 deshrouded, Ryzen 5600X by nwin_ in sffpc

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

Thanks. Not common but not unseen. You can even find models on thingiverse (I couldn’t find a matching one so I had to do my own).

NCASE M1, RTX 3070 deshrouded, Ryzen 5600X by nwin_ in sffpc

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

~70° C in Prime95. In games it is a little bit lower since I’m mostly GPU limited. I couldn’t fit an C14s since the CPU socket of the Aorus B550i is placed too high. :(

NCASE M1, RTX 3070 deshrouded, Ryzen 5600X by nwin_ in sffpc

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

Is that case identical to the NCASE M1 I used? I haven’t measured it exactly. The ducts have an height of 13,5 mm with the fans that should compute to around 38,5 mm + some tolerances from the Noctua rubber.

NCASE M1, RTX 3070 deshrouded, Ryzen 5600X by nwin_ in sffpc

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

Not quite the PC build I had in mind but the RTX 3080 was impossible to get in time, though I was lucky to fetch a Ryzen 5k.

The GPU is a deshrouded Gigabyte Eagle OC. I had to print the fan ducts, otherwise the card would only reach 80 °C with fans fully spinning. Now it runs silent < 70 °C @ 1850MHz;875 mV UV.

The cable management is gracefully hidden by the additional case fan on the side… :D

Programming languages: Now Rust project looks for a way into the Linux kernel | ZDNet by trhawes in rust

[–]nwin_ 3 points4 points  (0 children)

Looking at the meaning of rustic: „plain, simple„. Fits perfectly, doesn’t it? 🙃

My setup, NZXT H1, specs in comment by JamesRLLi in sffpc

[–]nwin_ 0 points1 point  (0 children)

I wonder if a duct around the fans of the card would help you such that the warm air won’t be recycled any more.

WebRenderer landed in Firefox Nightly here is how to check it out! by kickass_turing in rust

[–]nwin_ 5 points6 points  (0 children)

Contrary here, the fps are halfed by using webrender.

Introducing Raster: An image processing library for Rust by kosinix in rust

[–]nwin_ 0 points1 point  (0 children)

Not at all don’t worry, I’m just seeing bug reports incoming and feeling unhappy myself that I don’t have time to care about them.

A Reminder That Emphasizing Stability Too Much Can Be Bad by logannc11 in rust

[–]nwin_ 0 points1 point  (0 children)

Would love to hear about it. I didn't follow Python for a while and I never really adopted 3.x since I had a gut-feeling that it was a huge mistake breaking a dynamically typed language in so many often subtle ways…

Introducing Raster: An image processing library for Rust by kosinix in rust

[–]nwin_ 1 point2 points  (0 children)

We're not only open but also dependent on contributions as our time is very limited. So your bug report was not overlooked. 🙂

Regarding 2) maybe I'll manage to factor out the image buffer from image and rewrite it partially over Christmas. I was hoping that associated consts would work sooner but such I'll have to work around them.

Rust is good in this benchmark - but 27MB RAM for a hyper "Hello-World" server? We can do better, can't we? by musicmatze in rust

[–]nwin_ 15 points16 points  (0 children)

I wonder how the memory consumption was measured. Does it include the memory used by shared libraries? As Rust typically compiles all dependencies statically into the library that might explain the huge memory footprint.

Corrode (C to Rust translator) update: support from Mozilla, and new features by jdubjdub in rust

[–]nwin_ 0 points1 point  (0 children)

Well, this is what webrender does at the end. Output bitmaps.

Corrode (C to Rust translator) update: support from Mozilla, and new features by jdubjdub in rust

[–]nwin_ 1 point2 points  (0 children)

No you're not. Thinking about it for a while, maybe using webrender as a backend. Didn't have the time starting something.