flat assembler
Message board for the users of flat assembler.
Index
> IDE Development > memory management (fasmw) |
Author |
|
Tomasz Grysztar 09 Aug 2010, 08:35
It is often a case that you have to choose between speed and small memory usage (there may also exist some nice compromise between the two, but at the price of quite complex algorithm).
The AsmEdit control was written with an idea in mind that you should be able to comfortably edit even very large files, while still keeping the code relatively simple. This was achieved by eating up quite larger amount of memory (and a long load time for really huge files) - however after you load such file, you can edit it easily, just as comfortably as the small one - that was the idea. When I try opening that 53MB file with WordPad, the editing is so slow that it unusable for me. In fact once one of my friends who never had anything to do with assembly found fasmw very useful for editing some SQL dumps that he had trouble editing with other tools. PS. You can reduce the memory overhead by reducing the SEGMENT_DATA_SIZE constant of AsmEdit, however you must keep it large enough that single segment is able to contain the editor status variables (that is a small design flaw), their size is defined with "editor_status_size" label. |
|||
09 Aug 2010, 08:35 |
|
ouadji 09 Aug 2010, 09:21
Quote: It is often a case that you have to choose between speed and small memory usage ...speed, and memory usage ... a problem as old as the hills. I also have some compromises about this in wink. Quote: wordpad+53Mb file : the editing is so slow that it unusable for me Thank you for your reply Tomasz. |
|||
09 Aug 2010, 09:21 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.