Anyone w CPU 5.5-6.0 clock speeds to help run a PS test?

[Gene27167201cqus]

Hey guys ,

Does anyone have a cpu that has clock speeds of 5.5-6.0? (Even if being overclocked)

If so, I would like to ask if you could do a quick test in Photoshop, opening a new PSB file (20x29in, 600ppi, RGB 16bit)

And using a hard round at med & big size (compared to canvas as a whole)

start dragging around the canvas (doing dots as well) just to see if such a high clock speed can render the brush without lag.

I’m debating on whether or not to upgrade and so far a 3.2-> 4.2ghz upgrade hasn’t changed the lag for that size doc.

—————

Btw if possible could you do a quick screencaps as well just so we can see what the lag if any looks like?

Here’s mine so far at 4.2ghz

https://drive.google.com/file/d/1S0FMUpwxRAr9YZeNbliQEz48OCPd6HrB/view?usp=sharing

Build
https://pcpartpicker.com/user/jin098/saved/RVVV4D

[D Fosse]

This is probably more GPU dependent than CPU dependent. You should include different GPUs in that test.

[Gene27167201cqus]

@D Fosse  could you explain why gpu?

[Trevor.Dennis]

We have a test we have devised to compare systems

New document 30,000 x 30,000 pixels 8bit

Fully hard 5000 pixel brush with spacing set to 1%

Touch down in one corner, and shift touch in the diagonally opposite corner.

Restart Photoshop before doing the test to ensure the cache is clear

It helps to have Timing turned on in the Info panel, and show cross hair in brush cursor so you can be as accurate as possible.

I have an i9-13900K

RTX4080

64Gb RAM

Sratch space on a nearly empty 2Tb 980 Pro  Temp file is 11.4 Gb doing this test.

What's interesting is that my CPU sits at around 5.2Ghz at idle, but slows to about 4.8Ghz while performing the above test.  I've looked at everything with Performance monitor, and nothing appears to be remotely stressed, yet alone maxed out.

Looking at the Resource Monitor after dragging the brush around the screen creating a long winding worm to force some lag, CPU is peaking at 60%, Disk (scratch file) is doing nothing and nor is memory.  I'm guessing that Photoshop will not use 100% CPU cycles to keep the rest of the system running well.  Apps like Handbrake will max everything out.

[Gene27167201cqus]

@Trevor.Dennis 

Hi trevor i appreciate the testing, but im really only interested in the above specific case scenario.

with your setup do you notice any brush lag with the same scenario as I had in the video?

[Trevor.Dennis]

We prefer to use repeatable accurate testing, which is why we use corner to corner.  With the cursor crosss hair turned on to accurately hit the exact corner.

The image size panel does not show bit depth, but it is 16bit.

The pixel size is actually smaller than I expected. 

I set brush size to 3000 pixels because was about what can see in your video. The preset was fully hard, and spacing 1%

That gave me 3.3 seconds corner to corner.

I'm guessing that this is a test set up, and that you don't actually need a 600dpi 16bit document for your project?

[D Fosse]

While Trevor's test setup gives us a good way to directly compare*, I think we need to keep focus: do you experience lags that get in the way of working?

Even though I got a couple of seconds more than Trevor, it doesn't really matter in any practical way. There are no lags in practical work. I work in real time and the machine waits for me, I don't wait for the machine (except in some special cases where a lag is expected and will happen regardless).

The point I'm trying to make is that if there's lagging, this is probably not the reason.

In my experience, lagging is usually a symptom of a conflict of some kind. The prime suspect is always the GPU. Another common reason for problems is corrupt preferences (that's not "common" in general terms, but common explanation for problems).

*I got 8.6 seconds on i7-11700K and RTX 3060