Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

CauseWay DOS extender (Announce)

posted by DosWorld, 28.02.2025, 23:11
(edited by DosWorld on 28.02.2025, 23:32)

> Open Watcom one: dynamic
> memory management of the "DOS32" branch is exceptionally slow.

I am also saw this case.
It was a time when i have experiments with text editor (before dwed) and watcom c.
From my point of view, it is very bad implementation for malloc.

What i test:
I am measure time to load text file (huge work for malloc).
1. With watcom's malloc
2. With my own implementation for malloc/realloc/free. (at first, i am allocate one huge piece of memory with watcom malloc and then - use this memory for my own implementation of malloc/reallic/free).

My (very basic) implementation works fasten.
Then, i have idea about improve watcom library, ask question and see - my skills with dpmi is too low.

> I had receive big speed degradation for watcom's malloc,
> after 500k allocated strings. I think, it will be unusable after
> 1m malloc's. It is looks like watcom manage memory via linked list
> structure. So, I want refuse using watcom malloc and switch to
> my own memory manager (may be he not so fast, but he remember where
> is stored first free memory block).

win/linux has amazing memory managers - works like a cache/pool.

---
Make DOS great again!
Make Russia small again!

 

Complete thread:

Back to the forum
Board view  Mix view
22477 Postings in 2087 Threads, 400 registered users, 121 users online (0 registered, 121 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum