It requires us to create an “.etl” trace file, which we can be done using Windows Performance Recorder (WPR). Does the performance drop because we’re misusing Direct2D or DirectWrite? Does our virtual terminal (VT) sequence parser have any issues with quickly processing colors? We usually begin any performance investigations with Windows Performance Analyzer (WPA). Initially the culprit wasn’t immediately obvious of course. Initial investigation with Windows Performance Analyzer This drop is consistent and doesn’t get worse even with thousands of distinct colors. However, if we draw the same rainbow with 21 or more distinct colors it would drop down to less than 10 FPS. The one below has 20 distinct colors and could be drawn at around 30 FPS on my Surface Book with an Intel i7-6700HQ CPU. The performance issue could be replicated by repeatedly drawing a “rainbow” and measuring how many frames per second (FPS) we can achieve. A group of users were trying to implement a simple, terminal-based video game and found the performance under Windows Terminal to be entirely unsuitable for such a task.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |