Mi pc vs fps

#2 Con un i7 no debería de tener esto:
-threads 8 ?

Gracias por las respuestas.
-threads 4 no me bajan de 200
--threads 8 me va peor que normal

#5 tengo ese procesador y no le pongas -threads 8 porque el procesador no tiene 8 núcleos tiene 4. Otra cosa son los subprocesos pero en su día lo comprobé y me iba peor con 8 que con 4. Otra cosa es el +mat_queue_mode 2 hay gente que le sube fps, otros que no les sube nada y otros que les baja asik prueba.

#6 si desactiva el hyperthreading no va a poder usar todos los hilos cuando lo use para otra cosa o otro juego los necesite.

#7 Al menos antes daba ciertos problemas el HT, dudo que no siga igual (refiriendome a rendimiento en juegos y mas siendo motores antiguos)

Hombre si usualmente hace renders o cualquier cosa que tire de muchisimo procesador le diria que no desactivase el HT, pero como lo dudo yo desde luego lo haria y mas si busca rendimiento en el CSGO, pero vamos tan facil como probar.

#8 No, dos monitores no te va a afectar en nada, depende de las aplicaciones que tengas abiertas y lo que estes haciendo pero por lo demas no.

#1 300 fps los sacas con el rabo. Tengo un i5 4690K sin hacer OC y una r9 270x y me saca 300 fps muy facil en full hd con filtros x2 etc etc

Cuando pasan cosas asi es porque algo esta mal en el pc. Sin tocar nada con ese procesador deberias de sacar la vida de fps.

#14 Desactiva el HT y prueba.

Just because you can force it to run on more than 4 threads (which ideally each run on a different physical core) doesn't mean it will actually be faster, hell it might even be slower as you have more threads, which might stall CPU cores needlessly during context switches.

It's like asking 2 people to move a small box from A to B (by constantly having to stop and hand the box over to the other person), sure you can do it, but letting one person do it all is probably faster (even if that means that person runs at a 100% utilization load).

The hyperthreading of the i7 really doesn't help much either, sure it has double the amount of 'threads' (very misleading term IMO which often seems to confuse people) than their i5/i3 counterparts, but those only really help if you have an issue with pipeline saturation, which most games really don't have (especially older ones). Perhaps it actually helps mitigate performance loss from forcing more threads than is ideal (algorithms have sweet spots), but really hyperthreading shouldn't be a significant factor. Most of the performance difference (if not all) between the i7 and i3/i5 can be contributed to the slightly faster single core performance.

There are so many misconceptions and confusions about terminology/architecture/etc it's painful to read these topics over and over again.

No, just because your CPU has 'x threads' doesn't mean you should launch the game with that. These 'CPU threads' have little to no relation to that command line arg and saying you must match them up is complete nonsense.