Your malloc must pass all correctness tests before it will show up on the leaderboard.

Note: your placement on the leaderboard is not directly related to your grade (although it will point out awesomeness and awfulness). It's there to show you the tradeoffs associated with your implementation. If someone does something very sophisticated, it might translate to more overhead. Their score would be worse in the overhead column, but might be better in the performance or maintenance columns (coming soon).

There are two ranked colums:

• Overhead: sees how many small alloc requests your code can perform before returning NULL. (Allocates a 4K heap and then repeatedly requests 1 byte blocks. 255 means your heaplib was able to give out 255 1 byte blocks before it ran out of room.)
• Utilization: the maintenance test performs a series of alloc, resize, and free calls. Your score is how many of the alloc and resize requests did not return NULL.

---