[Paraview] FW: ParaViewWeb rendering performance

[Den Fairol]

Sorry for the hiatus. To hastily feed on Seb's curiosity, yes indeed the
behavior is blind to data source type. As for Aashish's concern, it is a
misunderstanding. I did mention I ran the client on VM, not the pvserver.
Thus discounting hardware as the root cause. Actually I just realized that
the 26 FPS was from the standalone ParaView (i.e. not connected to pvserver
as can be seen in the pipeline browser). Upon connecting to a local
pvserver, the FPS plummeted quite dramatically. Adjusting it to 'shared
memory/localhost' does the trick (more info here:
http://paraview.org/Wiki/ParaView/Image_Compressor_Configuration). The
obvious question would be, how can we do that in ParaViewWeb?

 

A second rather counter-intuitive question, why couldn't we see a degraded
image in ParaViewWeb when interacting with a polygonal object, it only
appears so in the VTK render window (first image is without interaction,
second is with interaction)? This observation does not reflected in ParaView
(i.e. you'll see the lost in quality during interaction). Ultimately how
much of this behavior (if any) impact the overall performance?

 

Regards,

Den

 

 



 



 

 

From: Aashish Chaudhary [mailto:aashish.chaudhary at kitware.com] 
Sent: 30 November 2013 4:56 AM
To: Sebastien Jourdain
Cc: Den Fairol; paraview at paraview.org
Subject: Re: [Paraview] ParaViewWeb rendering performance

 

If you are using VM or offscreen rendering, then it is likely that you are
not using hardware acceleration (depending on your setup, VM tool, and
hardware). A simple check using glxgears could give your more info. 

 

- Aashish

 

 

On Fri, Nov 29, 2013 at 11:38 AM, Sebastien Jourdain
<sebastien.jourdain at kitware.com> wrote:

Hi Den,

 

out of curiosity, does basic surface rendering with sample VTK dataset work
as slow? In other word, is it just the volume rendering that does not behave
the same?

I'm surprised to see a so huge difference in term of performance. 

 

Seb

 

On Fri, Nov 29, 2013 at 1:38 AM, Den Fairol <den.fairol at infovalley.net.my>
wrote:

Hi,

 

How can I improve the surface rendering performance of ParaViewWeb (besides
tweaking the still/interactive-image quality settings)? I could get a decent
FPS (26+/-) on ParaView (as depicted below) and ~50% decrease is naturally
expected when ported to ParaViewWeb (based on volume rendering of some
voxels). Unfortunately, the performance drop is much more critical than
initially presumed as I could barely scoop out 1 FPS. Do note that both
client and server are executed locally (i.e. if I launched the client
through a VM or remotely, then the low FPS will be further aggravated). The
dataset specifications are included at the bottom.

 

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

 


_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview





 

-- 
| Aashish Chaudhary 
| R&D Engineer         
| Kitware Inc.            
| www.kitware.com    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20140109/d396c0f3/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 162872 bytes
Desc: not available
URL: <http://www.paraview.org/pipermail/paraview/attachments/20140109/d396c0f3/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 177431 bytes
Desc: not available
URL: <http://www.paraview.org/pipermail/paraview/attachments/20140109/d396c0f3/attachment-0003.png>