29 June 2009, 16:18 | #1 |
Registered User
Join Date: Sep 2007
Location: Las Cruces, USA
Age: 71
Posts: 351
|
Multi Core Support Suggestion
All the testing I've done indicate the chip set emulation is actually pretty low overhead, it's the filtering that has high overhead. My suggestion is to move the native mode filtering and displaying to another thread to take advantage of multicore systems. It seems like the messaging would be minimal and as long as the cpu/chipset thread doesn't have to wait much on the filter thread the performance increase on mutlicore systems would be substantial.
So Toni, what do you think? Is this feasable? I have a 2gig 2 core system and I have to run every other frame when scaling to keep the cpu speed and fps up even with full screen. With windowed it's a lot worse. With filtering off it runs way better, almost as good as with RTG. |
29 June 2009, 22:55 | #2 |
Moderator
Join Date: Aug 2008
Location: Sidcup, England
Posts: 10,300
|
Hi Ed Cruse,
See the interview with Toni Wilen linked to in this thread: http://eab.abime.net/showthread.php?t=45681 particularly the discussion about multi-threaded programming. |
30 June 2009, 08:04 | #3 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,611
|
Option 1: Use D3D filter, it should be "multicore" as long as display driver and card is good enough.
Most filters are (afaik) mainly memory bandwith limited, not CPU limited so multithreading probably won't help because there still is only one memory bus for both cores. (and display data won't fit in CPU caches) I previously tried moving RTG copy/color space conversion code (which is similar to filtering code) to separate thread and didn't see any useful improvements, I assume this was also due to memory bandwith limit. Option 2: buy a new pc |
30 June 2009, 15:56 | #4 | |
Registered User
Join Date: Sep 2007
Location: Las Cruces, USA
Age: 71
Posts: 351
|
Quote:
I have a question about the D3D filter. I've used it and it's very fast, but the quaility of the display is very poor when scaling. I've found it works very good using windowed with automatic resize, with 1:1 scaling the quality is better then the Scale2x filter. Is the D3D filter supposed to be good quality and there's something wrong with my system or is poor quality normal with D3D when scaling? My computer isn't old enough yet. |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
PC Engine Core Grafx II + | ami_junkie | MarketPlace | 0 | 19 May 2012 14:49 |
For Sale: Core 2 Duo PC | PowerPie5000 | MarketPlace | 0 | 04 March 2010 17:00 |
Multi-Soundcard Support / Sound-Routing | SailorSat | request.UAE Wishlist | 1 | 17 July 2009 17:46 |
Deep Core maps | Retroplay | support.Games | 17 | 29 June 2009 10:08 |
Portaudio support (was: WinUAE support for ASIO drivers) | Amiga1992 | support.WinUAE | 57 | 28 March 2009 21:15 |
|
|