Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Some interesting test results, on an I7-4770k @ 3.5ghz
#21
(06-01-2014, 11:52 AM)Blyss Sarania Wrote: I believe it's EE + GS + Software thread + Extra threads.

Wow, so on a quad with HT, 1+4 software threads+EE thread+GS thread means it was working fastest with 7 threads in total(I'm assuming the last thread worked best handling background/OS stuff).

Never expected Pcsx2 to take advantage of HT that well.
<REDACTED>
Reply

Sponsored links

#22
(06-01-2014, 12:26 PM)Fezzer Wrote: Wow, so on a quad with HT, 1+4 software threads+EE thread+GS thread means it was working fastest with 7 threads in total(I'm assuming the last thread worked best handling background/OS stuff).

Never expected Pcsx2 to take advantage of HT that well.

Gabest did good job with multithreading.
Reply
#23
(06-01-2014, 11:52 AM)Blyss Sarania Wrote: I believe it's EE + GS + Software thread + Extra threads.

close, its EE + GS/Software Thread + Extra Threads. The base GS thread is always used for the mode it's in. So the emulator uses 2 threads generally unless you turn MTVU on, then it uses 3, then if you have 1 extra render thread it uses 4, but of course software mode is slow so the other threads spend a lot of time idle then, which is why setting it to 3 will make it use 4 cores more efficiently.
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#24
(06-01-2014, 03:18 PM)refraction Wrote: close, its EE + GS/Software Thread + Extra Threads. The base GS thread is always used for the mode it's in. So the emulator uses 2 threads generally unless you turn MTVU on, then it uses 3, then if you have 1 extra render thread it uses 4, but of course software mode is slow so the other threads spend a lot of time idle then, which is why setting it to 3 will make it use 4 cores more efficiently.

Does it distinguish physical cores from SMT ?
Reply
#25
(06-01-2014, 03:39 PM)Monochrome100 Wrote: Does it distinguish physical cores from SMT ?

It goes for physical cores first yes.
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#26
(06-01-2014, 03:43 PM)refraction Wrote: It goes for physical cores first yes.

So it working properly what was biggest problem in implementing multithreading like that in hardware mode ?
Reply
#27
Hardware mode just runs on the GS thread, which is provided by the main emulator itself.
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#28
(06-01-2014, 04:04 PM)refraction Wrote: Hardware mode just runs on the GS thread, which is provided by the main emulator itself.

Wasnt possible to add extra threads like in software mode ?
Reply
#29
No because the work is done on the GPU in hardware mode, where software mode does it on the CPU.
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#30
would it help to multithread the hardware mode? i just dove in the theory. multithreaded object creation for texture resources. could offload to stream textures while building the vertex lists. but i'd guess that'd bugger the already heavy texture cache implementation. Closedeyes
Reply




Users browsing this thread: 1 Guest(s)