Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Juraj

Pages: [1] 2 3 ... 319
Hah that's like the exact opposite I do :- D, but I think I just keep my default at 8/2 for almost any work (it's faster for IR/AI-Denoiser work too) and that gives me enough passes for 4-8K images (it also allows for more adaptivity re-comps)
I do find AA to be important always, imperfect AA is big CGI-giveaway to me, as cheap photo will be blurry mess, but it will never have that artificial edge 3D stuff has.

I always found this to be the case as well, although very minor, so I never really even bothered to do PS overlay to check. I thought it's byproduct of some order-of-operation or layering method, etc..

Less passes to look visually good, but also less passes for same noise, but never checked any formula :- ).

But this is good thing to pay attention, so you don't end up with too little AA done. Since high-res images don't need as many passes for GI/Light, they can for example end up being around 2-3perc. noise (visually clean) with only 25 passes for example, but roughly 100 passes are needed for really clean anti-aliasing from my experience.

Here is example of DDR5 RDIMM (the 'R' - Registered, is important) :

It's unfortunately whole magnitude more expensive than regular DDR5 memory. I personally didn't know this information few weeks back :- ) I don't really keep up that well now that all PCs are fast and I am not upgrading very often. I know a lot about children bicycles though.

There are also many generic variants that go for cheaper (here is example from few pages back from this thread, I am linking the 256GB version but I am pretty sure there is 128 as well.

TRX50, well, all Threadrippers (X and WX alike) now require Registered Memory modules same as Epyc. So that listed memory will not work.

Hardware / Re: Building a new workstation
« on: 2024-04-28, 15:37:12 »
I presume you mistyped Ryzen 7950X but no, it would not work like this. In particular:

7950X requires DDR5 memory instead of DDR4.

Working but suboptimal: 850 Watts. This is roughly enough for top CPU (like 7950X Ryzen) and GPU (4080) but transient spikes can cause it to overwhelm.
It's better to just go straight for 1000 Watts PSU and have peace of mind.

Hardware / Re: Threadripper issues
« on: 2024-04-28, 15:31:44 »
Super interesting. Are you testing local render times or DR&BB? And total frame times (Scene start-up, Precomp, Render, Denoise, Save, close-scene) or just pure speed in terms of Rays per Seconds?

I know from my experience the higher-core and more complex (multi-CPU,etc..) machines can for strange reason struggle with non-rendering aspects, particularly pre-comp processes can wildly swing. For that reason I often avoid Distributed rendering on complex scenes as the DR could take as long as 10 minutes or never even start due to some random bug.

Yeah I can understand, but now that devs have latest high-end dual-Epyc, let's see what happens :- ). There are lot of after-market Epycs on market so that would be quite good for studios if their performance becomes bulletproof in Corona.

That is not what I meant, there is nothing faulty with CPU. But that doesn't mean all software can utilize it in same way. How Embree can utilize the hardware depends on many aspects of software stack, from motherboard firmware to OS scheduler. If those things are written for retail SKU, tiny discrepancy can cause misutilization.

Years ago, one of such solutions was upgrading Visual Studio redistributable used for compiling. Just saying it isn't as easy as updating libraries often, though I do hope it is for this particular issue.

Perhaps not much else to do with left-over retail stock since most systems are built as all-in-one solutions. There might also be quite less interest in them compared to sourcing any available GPU stock.

I hope solution for your problem is found, but I will like to stress that if in some case you have non-retail stepping (ES/QS/etc..), the issue can be with on-chip memory controller which creates certain spiral of firmware/OS issues that can manifest under certain workloads (whether it's scheduler issues, CPU groups, NUMA nodes, etc..).

So if Corona team received fully retail unit (which in 2024 means all-in-one system for most Epyc stuff), they might not be able to replicate your issue.

It's bit risky proposition to build custom multi-CPU servers today, too many variables with zero support. Super hard to investigate and find what can be culprit.

Not saying that's the case, just be prepared.

Nice to know that Corona devs got the machine though.

Hardware / Re: PC Diagnostic software recommendations?
« on: 2024-04-16, 12:35:27 »
Nothing, X399 was dead-end platform, so no further options. And so was TRX40. AMD didn't do good job with keeping continuity sadly.

Any upgrade you might want, you will need to jump to new platform (CPU+Motherboard+DDR5).

2990WX was mostly very inconsistent with performance, it was heavily memory latency dependent (only half the cores can access memory, the other half have to go through that first half first).
It would work great under one situation, then badly under other..

Nowadays, that's no longer the case with any option on market. Even mainstream non-workstation platforms, like AMD Ryzen 9 7950X demolish the 2nd gen Threadrippers with 2x single-speed core, super consistent performance in every situation and can even support 192GB DDR5 memory, though it's bit tricky to get it work as well.

Hardware / Re: PC Diagnostic software recommendations?
« on: 2024-04-16, 12:13:14 »
I didn't want to say that, but I also thought that 2990WX is best relegated to history, it just wasn't good chip with its unique half-dies-only-mem-access architecture gimmick.

This is of course fully budget related, I also try to abide today with "if it works, keep it" instead of wasting money&time on latest&greatest stuff unless it's given to me for free.
But 2990WX was just mistake in retrospect.

Hardware / Re: PC Diagnostic software recommendations?
« on: 2024-04-15, 20:54:33 »
I am not aware of anything myself, but few things can be done:

1) Event Viewer (just type that into Windows Start menu). Particularly Windows Logs/System and then red-icon Kernel issues. But it is bit of like finding needle in hay since even the events themselves will simply tell you that certain driver caused crash for example, but nothing beyond that. It can sometimes provides good hint, esp. if it's driver related. And then you can do a bit of googling of that.

2) Hardware stability the biggest one being MemTest, tests stability of your memory. That was always massive Achilles heel of 2990WX. Can be run for hours ideally, overnight. Not much to do if it tells you that memory is corrupted. 2990WX is capable of running 128GB, even on low-end motherboards like Prime, even with low-end memory modules, but it requires very conservative setup. Like 2667 MT/s for example, instead of 2933/3200. I don't remember the tinkering fondly.

I have plenty of blue-screens with even the latest&greatest hardware. Sometimes it's random stuff like latest Windows 11 update no longer being friendly with ancient drivers for Realtek audio chip, or Intel LAN/Wi-Fi/Bluetooth driver, etc.. etc.. (Windows installs those drivers automatically, but those drivers are often dinosaur era)
And solution to that is endless uninstall/reinstall of random drivers.

wear and tear on the CPU

Never worry about this. By the time this happens, the CPU has morally aged beyond usability. No reason to worry about CPU lasting 15 years instead of 20.

Pages: [1] 2 3 ... 319