Apex Runtime Update for Developer Edition Orgs

By Steve Bobrowski | Published: December 6, 2011

ApexForce.com Developer Edition organizations will soon have a new Apex runtime. Read on to learn more.

On Friday, December 16, 2011 In January 2012, Force.com Developer Edition (DE) organizations will have a new Apex runtime that compiles directly to Java bytecode. This modification will deliver significant improvements in performance and scalability. And most orgs won’t have to change a line of code — everything will simply continue to work as it does now, only faster.

[UPDATE (December 19, 2012): Due to some internal requirements, the roll out of the new Apex runtime in DE orgs has been postponed until January 2012. Check back here for updates as they become available. Sorry for the delay. --Steve]

The new runtime implementation also means that each Apex method will now be bound by the Java bytecode limit of 64K. While this new limit is sizeable and adequate for all sensible methods, orgs that have methods exceeding this new limit will require attention.

We’ve already identified orgs with exceedingly large methods, notified them directly, and given them instructions on how to handle most situations. Unless you’ve received such a notification at your org’s primary email address, you’re in the clear. If you have received a notification, please take action before we implement the new runtime, as instructed.

In any case, if you are concerned about your org’s Apex routines, it’s really simple to confirm that everything is running smoothly. After Friday, simply run all tests in your org. This action will force a compile of all your source files and flag any class/trigger that is outside the new runtime limit.

We hope you enjoy the performance benefits of the new Apex runtime.

tagged , , , Bookmark the permalink. Trackbacks are closed, but you can post a comment.
  • http://twitter.com/fractastical Joel Dietz

    I feel the need, the need for speed!!!

  • Anonymous

    Is there any plan to use the new runtime in other org types? If so, any plan/idea/indication of when?

    Cheers!

  • http://twitter.com/zachelrath Zach McElrath

    I’m a big fan of performance-boosting updates that don’t break everything.

  • http://twitter.com/radnip Francis

    The orgs I look after are too complex/large (FinancialForce etc) to be able to use dev orgs is it possible to run the tests on full sandboxes?

  • http://blog.superpat.com/ Pat Patterson

    If you’re curious and you want to know if your org is running on bytecode, then just do

    System.debug(‘Heap limit ‘+Limits.getLimitHeapSize());

    from execute anonymous or in a context other than a batch or future method. You’ll see 6000000 for bytecode-enabled orgs and 3000000 otherwise.

  • http://twitter.com/mjgallag24 Michael Gallagher

    here’s hoping this is a very small step that’s just beginning to open the door to the possibility of writing triggers in java someday :)

  • http://twitter.com/mjgallag24 Michael Gallagher

    doesn’t look like this happened for my current dev org on na12, based on checking the heap size limit, haven’t checked any other instances, anyone see it enabled in their dev orgs yet?

  • http://blog.superpat.com/ Pat Patterson

    My na9 is still showing 3000000 for Limits.getLimitHeapSize() too. I’ll see what I can find out…

  • http://twitter.com/mjgallag24 Michael Gallagher

    thanks Pat, appreciate it

  • http://twitter.com/tmatthiesensfdc Taggart Matthiesen

    Apologies – we actually moved the date to this Friday – December 16th. As it will be a rolling enablement, I would check your org on Monday, December 19th. Thanks and apologies for the confusion.

  • http://twitter.com/ca_peterson Chris Peterson

    Holy crap, double the heap size? AWESOME

  • http://blog.superpat.com/ Pat Patterson

    Note – as Taggart mentions elsewhere in these comments, the switchover is now scheduled for this Friday, but it will be a rolling enablement – check your org next Monday, 12/19.

  • http://twitter.com/TehNrd Jason Venable

    My dev orgs that are still seeing 3MB for heap. Is this only enabled for newly created dev orgs?

    Yet, I am also seeing a sandbox that appears to have already be updated.

  • http://twitter.com/TehNrd Jason Venable

    Nevermind, I see Taggarts reply below indicated this change will be done on the 16th of Dec.

  • http://twitter.com/tmatthiesensfdc Taggart Matthiesen

    Sorry all, we are holding off the launch of the new runtime until early next year. We will keep you posted as we get closer to the revised launch date.