F5F Stay Refreshed Hardware Desktop The typical FCLK inquiry 🤔

The typical FCLK inquiry 🤔

The typical FCLK inquiry 🤔

Pages (2): 1 2 Next
J
jpc2002
Member
52
11-12-2016, 08:46 PM
#1
Looking for credible evidence on performance drops when memory clock exceeds fabric clock? I found several comparisons between Cinebench results for different configurations. Running the same multicore test three times on each setup confirmed the trends. The 3666/1800 achieved a higher score, supporting the idea that pushing memory clocks too high can impact overall performance. While I haven’t overclocked fabric clocks beyond 1800 yet, this aligns with current findings. It seems some tests even reached 1900MHz on FCLK, though that was done in Linus’s videos. For fabric clock limits, stick to what Cinebench shows as realistic.
J
jpc2002
11-12-2016, 08:46 PM #1

Looking for credible evidence on performance drops when memory clock exceeds fabric clock? I found several comparisons between Cinebench results for different configurations. Running the same multicore test three times on each setup confirmed the trends. The 3666/1800 achieved a higher score, supporting the idea that pushing memory clocks too high can impact overall performance. While I haven’t overclocked fabric clocks beyond 1800 yet, this aligns with current findings. It seems some tests even reached 1900MHz on FCLK, though that was done in Linus’s videos. For fabric clock limits, stick to what Cinebench shows as realistic.

A
APsixYT_
Junior Member
17
11-13-2016, 05:26 AM
#2
Topic cleaned = Don't take over other subjects.
A
APsixYT_
11-13-2016, 05:26 AM #2

Topic cleaned = Don't take over other subjects.

T
TheLaurenzo
Member
59
11-13-2016, 07:58 AM
#3
This result is quite close to what we expect, and Cinebench doesn’t focus much on available RAM.
T
TheLaurenzo
11-13-2016, 07:58 AM #3

This result is quite close to what we expect, and Cinebench doesn’t focus much on available RAM.

J
JebThePleb
Posting Freak
898
11-13-2016, 01:13 PM
#4
No evidence confirms the clocks are fully independent, which raises concerns about increased latency and performance drops. If Cinebench isn't reliable, consider using other benchmark tools like AIDA64 or 3DMark for more accurate results.
J
JebThePleb
11-13-2016, 01:13 PM #4

No evidence confirms the clocks are fully independent, which raises concerns about increased latency and performance drops. If Cinebench isn't reliable, consider using other benchmark tools like AIDA64 or 3DMark for more accurate results.

T
Tavado
Senior Member
505
11-13-2016, 03:42 PM
#5
Synchronize once more and execute the latency test in Aida64. After that, isolate components and re-test.
T
Tavado
11-13-2016, 03:42 PM #5

Synchronize once more and execute the latency test in Aida64. After that, isolate components and re-test.

M
mat_fram
Posting Freak
776
11-27-2016, 11:49 PM
#6
Have you considered paying for Aida64? If not, I'll look into it, thank you!
M
mat_fram
11-27-2016, 11:49 PM #6

Have you considered paying for Aida64? If not, I'll look into it, thank you!

C
CreeperKing439
Junior Member
45
12-02-2016, 07:21 PM
#7
Yes, but there is a free trial.
C
CreeperKing439
12-02-2016, 07:21 PM #7

Yes, but there is a free trial.

D
droide12046
Junior Member
18
12-03-2016, 02:47 AM
#8
Your theory holds true. Decoupled introduces greater latency compared to Coupled. However, it's possible that pushing the Memory clock even further than the FCLK could reduce latency. Linus mentioned this too; I plan to explore it and share more insights soon. The gap between MCLK and FCLK seems substantial.
D
droide12046
12-03-2016, 02:47 AM #8

Your theory holds true. Decoupled introduces greater latency compared to Coupled. However, it's possible that pushing the Memory clock even further than the FCLK could reduce latency. Linus mentioned this too; I plan to explore it and share more insights soon. The gap between MCLK and FCLK seems substantial.

I
iRaine
Posting Freak
800
12-05-2016, 03:41 AM
#9
Latency decreased slightly, though not significantly. Coupling proved most effective for reducing delays. However, very large variations could yield improved outcomes.
I
iRaine
12-05-2016, 03:41 AM #9

Latency decreased slightly, though not significantly. Coupling proved most effective for reducing delays. However, very large variations could yield improved outcomes.

J
jjane1227
Junior Member
39
12-26-2016, 08:42 PM
#10
Reduced FCLK to 1600 while keeping MCLK at 3800MHz produced poorer outcomes. Planning to test a lower MCLK with higher FCLK next.
J
jjane1227
12-26-2016, 08:42 PM #10

Reduced FCLK to 1600 while keeping MCLK at 3800MHz produced poorer outcomes. Planning to test a lower MCLK with higher FCLK next.

Pages (2): 1 2 Next