[RESOLVED] Algorithm speed after compiled

[Episcopal]

Hello everybody

I know that when we compile the program it runs faster than in development mode in the IDE.
The problem here is that I put a TIMER to measure the speed, and an MSGBOX to display the results.
In design mode and after compilation, the speed is the same.



Regardless of the code, it shouldn't be faster after compiling.

[Episcopal]

Dim vTimer As Single
    	vTimer = Timer

	Do
        newStartPos = SendMessageLong(m_Settings.EditHwnd, EM_FORMATRANGE, False, _
                VarPtr(m_Settings.FormatRange))
      
        If newStartPos >= TextLength Then
            Exit Do
        End If
        m_Settings.FormatRange.mCharRange.firstChar = newStartPos
        iPageCtn = iPageCtn + 1
   	Loop

	MsgBox Timer - vTimer

[Arnoutdv]

There is nothing where speed can be gained. All time is in the external calls

[Episcopal]

I did a test with Microsoft Office Word 2021 and it also takes a long time to count the pages.
I put a document with 15,000 pages in the quoted Word.... and every letter typed it crashes for a while.

[couttsj]

You need to force higher precision in the calculation, and you have to realize that there is a minimum because of the Tick Counter.

Dim Start as Double
Start = Timer
..
..
..
Debug.Print "Time: " & (CDbl(Timer) - Start) * 1000 & " ms"

For more information, see:
https://www.vbforums.com/showthread....recision-Timer

J.A. Coutts

[Episcopal]

Thanks JA Coutts for the link, I'll definitely check it out...

But the real problem is the algorithm I posted, because if you insert a document with more than 15000 it crashes for a while, even in Word 2021.

But I will implement STimerEx for better measurement.

[Episcopal]

Office Word 2021 is still slower than my component.

[wqweto]

The “algorithm” you are using is trivial (a single loop) and this cannot be further optimized. The only option would be to stop using EM_FORMATRANGE which does not sound feasable. It is this message impl that a million more things are done than in your “algorithm” and you cannot optimize EM_ FORMATRANGE external implementation.

[Episcopal]

Arnoutdv and wqweto, you are right. The API call cannot be changed because "it" is outside of my system, so I didn't see any difference in time between design and compiled mode.

Come to think of it, there's nothing you can do.

The only option would be to stop using EM_FORMATRANGE which does not sound feasable.

qweto there is a replacement for EM_FORMATRANGE???