• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
  • entries
    625
  • comments
    1446
  • views
    1006497

Improving memory allocation patterns in the Epoch compiler

Sign in to follow this  
Followers 0
ApochPiQ

457 views

As part of my ongoing effort to make the Epoch compiler idiotically fast, I've turned my attention to one of the primary killers: dynamic memory allocations.

Part of this is unavoidable, since dynamic memory has to be allocated when constructing the parse tree. But for some reason, I kept seeing really large numbers of allocations in places that just didn't warrant them. My first hunch was that I just needed to replace the allocation with something faster; so I wrote a quick linear allocator that would just spam allocations into a massive, pre-sized buffer, and then throw the whole thing away after compilation finishes.

After some hiccups, I got the whole thing to build (which takes forever now) and ran the first test. Paradoxically, it made no difference to execution speed, and it increased memory usage far more than it should have. Worse, I'm running only release-mode builds, because debug builds literally can't cope with my sample input in less than an hour or so. (That's how much excess cruft qi generates... eurgh.) This means that my profiler can't see true call stacks, but rather has to cope with the maze of semi-collapsed templated inline calls that fill the parser.

It took forever, therefore, to make a simple discovery that's had me kicking myself for several minutes now.

The AST structure for Epoch makes heavy use of boost::variant. The AST is also self-recursive, meaning that several nodes are defined in terms of themselves. This necessitated (at one point) the use of boost::recursive_wrapper<> to ensure that the compiler could figure out the circular definitions.

That requirement went away a long time ago when I started doing deferred construction of AST nodes using my own wrapper template; but I never updated all of the uses of recursive_wrapper, because they never showed up in profiling - just allocation calls.

Out of random curiosity and frustration, I finally cracked open the code for recursive_wrapper to see how it does its magic.

Yep, you guessed it: it dynamically allocates the contained type.

That means that I'm not only allocating memory for the AST nodes, I'm allocating memory for the deferred variant that points to that AST node - and adding a level of pointless indirection to boot.

The good news is, removing recursive_wrapper isn't too hard, and speeds things up, although just a tiny bit.

The bad news is, now I have a rampant memory leak, and I'm utterly stumped as to why.


One step forward, thirty steps back, it seems.

0
Sign in to follow this  
Followers 0


5 Comments


AAAAAAAAAARGH I CANNOT BELIEVE HOW STUPID I AM.

Rule Number One of writing a linear allocator in C++: you still have to manually invoke destructors even if freeing the memory is a no-op.
0

Share this comment


Link to comment
So what are the parse times down to now?
And for the record, how long exactly does it take to compile the compiler?
0

Share this comment


Link to comment
Compiling the compiler from scratch takes about 25 minutes on my laptop, which is what I've been doing all my work on recently. I really need a beefier laptop... or I need to get off my lazy ass and unpack my Core i7 workstation that I [i]used[/i] to do all of this on before I moved.

Anyways! Parse times are hovering around 15ms, which isn't really much of an improvement considering how much work I've sunk into the last few tweaks, so obviously I've run smack into the wall of diminishing returns and it's questionable how much more effort is justified.



But I'm a total addict, so I'll probably run a few more profiles on it and see if there's any stragglers of sluggishness that I can banish.
0

Share this comment


Link to comment
You know, im pretty sure a few years ago that you yelled at me for getting too caught up in premature optimizations... I think you should take that piece of advice! I want to see more features dagummit! But geez whats up with those compile times, are you building Boost too??? Thats crazy!

Anyways, can you please get back to adding awesome-ness-tic features to the language :) Pretty please!? KTHX.
0

Share this comment


Link to comment
Hey, this is hardly premature - if anything it's long overdue. The Epoch compiler has been painfully slow for way too long, and now that I'm dogfooding it pretty heavily with Era development, I want my iteration times to be faster. This is also groundwork for adding a realtime syntax highlighting component to Era that does things like color variable and function names automatically. (The current syntax highlighter is totally unaware of the semantics of Epoch programs.)

So yeah. This is all to [i]enable[/i] the next round of juicy features. The faster I can compile Epoch programs, the faster I can churn out new features for those same programs :-)
0

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now