CPU Database

[ALEXM931]

What is your underlying question when you need to go through more than 100 search results? Not what you search for, but the result you are looking for

for exemple when i search for am3 cpu there are 105 of them but only 100 of them are listed in the search

 

[datnoz]

not related to the cpu database but to the gpu one, but posted here since there don't seems to be one.
would it be possible to specify what DVI outputs are one the gpu like dvi-i/a/d and the link width (double ou single).
and maybe even the compatibility with DP++?

 

[rahlquist]

The new search is a work in progress. You can still select all the same filters though, none of them went away.

Any suggestions to improve the search experience?

Visual examples? When I am digging for info, I want to do it fast. Drill down with drop downs is quick and easy.

Allow me to expand. So I came today to look for AMD cpu with integrated graphics released in 2024- 2025 close in capability to Z1e.

Get to CPU page, choose integrated graphics/yes

Try to get a release year of 2025 nope. nothing beyond 2018 it looked like.

So I drop the IGPU setting, and start trying to finesse out the answer I want, and I get throttled and captcha'ed etc.

In the old UI I could make selections before submitting, see whats available and not have to hunt and peck so much.

 

[Fouquin]

Get to CPU page, choose integrated graphics/yes

Try to get a release year of 2025 nope. nothing beyond 2018 it looked like.

@W1zzard This looks like a bug. The "Yes" and "No" options for IGPU are showing opposite results, but not universally. That is very strange.

This is what I meant by work in progress. The new search is a pretty large departure in design both front and back, so some interesting (and admittedly frustrating) bugs have appeared.

The rate limit was increased somewhat substantially to stop serving captcha on every search, it may need to be increased again?

 

[Mangle7450]

Please complete your CPU database of processors based on PowerPC and ARM architecture, that would be great!

 

[Dragonlord]

The new search is a work in progress. You can still select all the same filters though, none of them went away.

Any suggestions to improve the search experience?

I have some suggestions, if that's alright.

The old search had further filters such as whether or not a CPU was for mobile platforms, server platforms, CPU clock speeds, and I believe cache sizes as well (though I may be misremembering that last part). All of these are/were incredibly useful, and I'd love for them to be added back, as I currently don't see any way to access them with the current UI.

You mention that all of the old filters are still accessible, am I missing some setting to go back to the old UI while new this one is worked on?

 

[W1zzard]

was for mobile platforms, server platforms

check "Target Market"

CPU clock speeds

Sure, I can add that. How would you split them into ranges? What's the plan for E-Clocks? Included? Pick the higher? the primary core?

100, 400, 450, 475, 500, 533, 550, 570, 600, 650, 667, 700, 733, 750, 800, 850, 866, 900, 933, 950, 1000, 1050, 1053, 1066, 1067, 1073, 1100, 1133, 1200, 1238, 1250, 1266, 1300, 1333, 1334, 1350, 1400, 1450, 1463, 1466, 1467, 1480, 1500, 1533, 1550, 1580, 1583, 1600, 1650, 1660, 1666, 1667, 1700, 1730, 1733, 1750, 1800, 1826, 1830, 1833, 1834, 1860, 1862, 1866, 1867, 1877, 1900, 1910, 1917, 1992, 2000, 2050, 2083, 2100, 2130, 2133, 2150, 2160, 2166, 2167, 2170, 2200, 2250, 2260, 2261, 2266, 2267, 2300, 2333, 2394, 2400, 2450, 2500, 2527, 2530, 2533, 2534, 2550, 2600, 2650, 2660, 2666, 2667, 2677, 2700, 2750, 2790, 2793, 2800, 2830, 2833, 2850, 2900, 2930, 2933, 2950, 3000, 3050, 3060, 3066, 3067, 3100, 3150, 3166, 3167, 3200, 3250, 3300, 3333, 3334, 3350, 3400, 3466, 3467, 3500, 3550, 3600, 3650, 3667, 3700, 3730, 3733, 3800, 3850, 3900, 4000, 4050, 4100, 4200, 4300, 4400, 4500, 4700

cache sizes

Same question for cache sizes

old

The old search engine has been retired

 

[Dragonlord]

check "Target Market"

I missed that, thanks.

Sure, I can add that. How would you split them into ranges? What's the plan for E-Clocks? Included? Pick the higher? the primary core?

For splitting the clock speeds, I'd imagine something like half-gig steps would make sense? Like "2GHZ - 2.5", "2.6 - 3", "3 - 3.5", so on. That way it isn't too cluttered, and is still specific enough for those searching.
Maybe E-Cores would have their own filter? But I have no idea how much of a headache that would be to implement.

Same question for cache sizes

I'm not entirely sure what would work best for these. Cache sizes are specific enough that (IMO) it warrants having individual options for each size, but again I have no idea how difficult / time consuming that is to implement, nor how taxing it may be on the site servers. Plus it may look bad, if aesthetics matter.

 

[W1zzard]

I'm not entirely sure what would work best for these. Cache sizes are specific enough that (IMO) it warrants having individual options for each size, but again I have no idea how difficult / time consuming that is to implement, nor how taxing it may be on the site servers. Plus it may look bad, if aesthetics matter.

User experience is always my highest priority, but as you mention correctly, I also have to balance vs my dev time, and server resources aren't unlimited either, but nowadays it's pretty close We switched from some self-built search engine to Typesense and it's like magic.

I guess with "Cache Size" you really mean "L3 Cache Size" ?

like half-gig steps would make sense

https://imgur.com/A2qWbt6

Yeah, this is mostly workable. I guess "Under 1 GHz" and "Above 5 GHz" would make sense?

https://imgur.com/lmsnzbq

This is actually pretty much perfect

 

[Dragonlord]

I guess with "Cache Size" you really mean "L3 Cache Size" ?

Oh yeah, L3 is what I meant, thought I specified lol whoops.
L1 / L2 sizes might matter to somebody, but I'm not entirely sure it's worth whatever amount of dev time it would take, given how standard those sizes are nowadays.

This is actually pretty much perfect

Those ranges look great, that's all I'd need, and I'd assume all anyone else would likely need.

 

[W1zzard]

L1 / L2 sizes might matter to somebody, but I'm not entirely sure it's worth whatever amount of dev time it would take, given how standard those sizes are nowadays.

Good point, and I agree, so I'll expose L3 Cache Size only

Bonus question, could a search filter like "Hybrid Architecture" be interesting? CPUs that have P- and E-Cores, but how to treat Zen 4c, which I'd probably say is not a hybrid arch

 

[Dragonlord]

Bonus question, could a search filter like "Hybrid Architecture" be interesting? CPUs that have P- and E-Cores, but how to treat Zen 4c, which I'd probably say is not a hybrid arch

A Hybrid filter could be useful, for people looking for Intel CPUs that don't / do split between P and E, though I'm not sure if there's any other similar "hybrid-style" chips?
Though it may be a good filter to already have for "future-proofing" the site, in case other hybrids appear (if there aren't already others I'm just not aware of).

On Zen 4C, as far as I remember those are just smaller / arguably weaker versions of the normal Zen 4 style, with lower clock speeds and lesser L3 caches, so I'd say those aren't hybrids.

 

[W1zzard]

for Intel CPUs that don't / do split between P and E

Good idea

 

[W1zzard]

Added L3 Cache and Frequency. Is that what you had in mind?

 

[Onasi]

@W1zzard
Works great. One nitpick I have and what I am a bit missing from the old search layout is that when filtering by Codename or Generation the list is now just alphabetical of all chips instead of segmenting CPUs into market segments and/or series. Any plans on re-implementing that?

 

[W1zzard]

@W1zzard
Works great. One nitpick I have and what I am a bit missing from the old search layout is that when filtering by Codename or Generation the list is now just alphabetical of all chips instead of segmenting CPUs into market segments and/or series. Any plans on re-implementing that?

Probably not, people who know just the codename will have to scan an unknown number of multiple sections, that are each alphabetically sorted.

Just click mfgr = amd and your codename list is filtered instantly

 

[Onasi]

@W1zzard
That’s fair. Another thing that I wanted to bring up with even the old search is a bit of odd terminology used - the Generation term. I am still unsure that it’s used in a way we are using it commonly. Using a filter of Intel-Generation-Core i7 and getting a list of all i7s or AMD-Generation-Ryzen 5 and getting all R5s regardless of architecture or what Intel and AMD both consider actual generations seems a bit… unintuitive? May I suggest switching the term to maybe something like “Model range”?

 

[W1zzard]

seems a bit… unintuitive?

yeah, that's how we have them in the backend though, a bit complicated to change

 

[Dragonlord]

Added L3 Cache and Frequency. Is that what you had in mind?

Looks and works great, thank you for your work.