Skip to main content

Further Optimization Analysis

Calvin made a post about code optimization and noted that if you actually attempt to do a
FOR i = 1 TO num
IF wParam=ASC("a")

It would take longer than just using the direct values. So what happens if you used variables or #DEFINE statements.

I first thought "i'll use constants" , adding the following

#DEFINE cn1 ASC('a')
#DEFINE cn2 ASC('b')

and changing the logic to:
FOR i = 1 TO num
IF wParam=cn1

The Result? A little faster but nowhere close to the performance improvements gained by using the literal values. Why? Because it is simply replacing the cn1 and c2 with the ASC('97') statements.

But even when I changed the #DEFINEs to variables and assigned the values, they still weren't improved.

The only time it came close was if I explicitly did
#DEFINE cn1 78
#DEFINE cn2 79

Here's a basic breakdown (non scientific) of my times:
With literal values: 3.781 seconds
With functions: 5.187
With variables: 5.11
With DEFINEs and Functions: 4.98 - 5 (I did run it twice)
With DEFINEs and Literals: 3.782 seconds

So the rule has to be - if you can avoid using functions and variables by using constants or the literal values, do it.

Optimization...go figure.


Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…