• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Isn't a Griffon application too slow to run?

 
Ranch Hand
Posts: 701
2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is Griffon too slow when running, or this is because of Swing?
 
Bartender
Posts: 5167
11
Netbeans IDE Opera Java
  • Likes 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Did you actually find it slow, or are you just guessing? Any Swing application that's slow is probably just badly coded.
 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi!

I asked a similar question. See https://coderanch.com/t/549501/GUI/java/Griffon-user-interface-responsiveness-compared.

Fredrik
 
author
Posts: 47
VI Editor Java
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Too slow to do what exactly? Is it because of the choice of Groovy as glue language?
I'm happy to say that the answer is no. Most of the Griffon runtime is written in Java, which means that the inner workings are as fast as your vanilla Java framework. There are parts of the code that use Groovy APIs, most of those APIs happen to be written in Java too.

Does this mean Griffon is as fast as a Java framework? No, it is not, but it's definitely not as slow as you might think. If you write MVC members in Groovy then you're subject to the Meta Object protocol, i.e, dynamic method dispatch. What happens is that instead of getting a direct method invocation you follow (automatically) a more elaborate decision tree to find out the right method to invoke. This is where the "slowness" of Groovy appears. In practice Groovy code can be +50% slow than Java, which only comes into play if you're doing computation intensive tasks like number crunching as most of the times the responsiveness of an application is measured by its weakest link: I/O.

Cheers,
Andres
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic