Posted by gouessej on Apr 21, 2015; 8:08am
URL: https://forum.jogamp.org/VBO-Performance-Misunderstanding-tp4034319p4034348.html

Hi

At first, please switch to JOGL 2.3.1. You're still using an old version. It won't be enough to solve your problem but you might fall on a fixed bug. Using an old version is a waste of time. Don't forget to modify the imports:
https://jogamp.org/bugzilla/show_bug.cgi?id=682

Secondly, I advise you to follow Wade's advice, it would help to find the culprit.

Thirdly, look at GL2ES3.GL_MAX_ELEMENTS_VERTICES. If your VBOs are too big, it will slow down your rendering. Break them into smaller ones, for example store about 1000 vertices per VBO.

Fourthly, as you use a single VBO, why not binding it once for all and never "unbind" it at least for your test?

Finally, post the complete stack trace of the GL exception GL_INVALID_VALUE. Are you sure that you want to call the relative put() method? In my humble opinion, there is something wrong in updateVBO() but it doesn't impact the performance.