performance - Perfomance of the PAGE_WRITECOPY windows internal memory -


i need implement undo-redo feature in application, reads project file , makes sequence of separate transactions changing project's content. project can hundreds mb large.

my idea implement undo-redo on basis of copy-on-write (page_writecopy) memory mechanism. assume after end of transaction application can access both changed , unchanged pages, compare them, identify changed records, store original record states in dedicated undo stack, free created non-changed pages , restore write-on-copy protection of changed pages. have 2 questions:

  1. how , can found addresses of original (non-changed) pages.

  2. the awaited performance of such implementation?. middle size of project's records cira 100 bytes. if transaction changes 3000 records may involve change of 100 or more 4k physical pages. write-on-copy memory performant enough support routineous change of hundreds physical pages on each step?


Comments

Popular posts from this blog

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -

Trying to import CSV file to a SQL Server database using asp.net and c# - can't find what I'm missing -