One of the cool new features of the JavaFX 2.2 developer preview release is a new Canvas node that allows you to do free drawing within an area on the JavaFX scene similar to the HTML 5 Canvas. You can download this release for Windows, Mac, and Linux from JavaFX Developer Preview.

Being adventurous, I decided to take the JavaFX Canvas for a spin around the block. In doing some searching for cool HTML 5 Canvas examples, I came across Dirk Weber's blog comparing performance of HTML5 Canvas, SVG and  Adobe Flash,An experiment: Canvas vs. SVG vs. Flash. This looked interesting for a Canvas beginner as I am, so I decided to copy his implementation and see how it runs in JavaFX.

This turned out to be pretty straight forward. Dirk's original JavaScript application for the HTML 5 Canvas contained a spirograph drawn at the top of the screen with 4 sliders beneath it for changing the number of rotations and particles  and the inner and outer radius for the spirograph. Also, at the top is a text display showing the frames-per-second after the image is drawn. By manipulating the slider properties, the spirograph is drawn differently and each time the performance is shown in frames per second. 

To do the same thing in JavaFX,  I first created a JavaFX Application class, with a Stage and Scene and placed the Canvas at the top of the scene with 4 sliders below it followed by a Label to report the frames per second as defined in Dirk's original JavaScript implementation. One change I made to Dirk's implementation was instead of using Arrays of doubles for points, I used the JavaFX Point2D class. 

My original goal was just to become familiar with the JavaFX Canvas object, but as I played around I noticed something about the performance. When I ran Dirk's HTML 5 and Flash version I would get a consistent frame-per-second rate of 50-70 fps when I adjusted the sliders (Mac OS X 10.7.4, 2.6 GHz Intel Core 2 Duo, 4 GB ram). However, when I ran my JavaFX version, the first time after starting, it drew the spirograph in the low 40s fps. But I noticed that when I adjusted the sliders, the performance got better. First adjustment, low 80s fps; fifth adjustment, mid 120s; a few more and I was getting 1000 fps, and eventually Infinity fps. I didn't believe the Infinity reading, so I debugged to the code, only to find out that it took less than a millisecond to calculate and draw the spirograph.

I assume that this behavior reflects the Hotspot compiler kicking in after a few iterations of the Spirograph calculation. But, it sure is fast. 

The JavaFX source can be downloaded from here: 

SpiroGraph.java

SpiroCanvas.java

Views: 3911

Comment

You need to be a member of Codetown to add comments!

Join Codetown

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

Article: Beyond Memory Safety: What Makes Rust Different – Lessons from Autonomous Robotics

This article explores that question through the lens of a real-world Rust project: a system responsible for controlling fleets of autonomous mobile robots. While Rust's memory safety is a strong foundation, its true power lies in the type system and ownership rules. The session will go beyond memory safety and explore ways to encode behavior and protocols directly into types.

By Andy Brinkmeyer

War in Iran Damages Multiple AWS Data Centers, Challenging Multi-AZ Assumptions

Earlier this month, Iranian drone strikes damaged three AWS data centers in the UAE and Bahrain, causing outages and disruptions to multiple services. The events, which affected multiple facilities within the same AWS region, sparked discussion in the community about how geopolitical conflict can directly impact global cloud infrastructure and multi-AZ deployments.

By Renato Losio

QCon London 2026: Uncorking Queueing Bottlenecks with OpenTelemetry

At QCon London 2026, Julian Wreford and Oli Lane from Gearset showcased how distributed tracing and SLOs solve asynchronous observability gaps. By shifting from queue-size metrics to latency-based alerts, the team improved incident response. Key technical takeaways included using OpenTelemetry trace state for async duration tracking and wide events to uncover hidden architectural waste.

By Mark Silvester

QCon London 2026: Ontology‐Driven Observability: Building the E2E Knowledge Graph at Netflix Scale

Prasanna Vijayanathan and Renzo Sanchez-Silva, both Engineers at Netflix, presented “Ontology‐Driven Observability: Building the E2E Knowledge Graph at Netflix Scale” at QCon London 2026, where they discussed the design and implementation of an end-to-end knowledge graph that models the Netflix user experience.

By Michael Redlich

QCon London 2026: From DVDs to Global Streaming How Netflix’s Commerce Architecture Actually Evolved

Dynamic principal engineer at Netflix, Kasia Trapszo, expertly navigates the evolution of the company’s commerce architecture from a DVD rental service to a global streaming giant. Her insights on pragmatic adaptations to billing systems reveal invaluable lessons on agility, localization, and the complexity of modern payment landscapes.

By Daniel Curtis

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service