# ParaView saves state py file, it takes too long

**URL:** https://discourse.paraview.org/t/paraview-saves-state-py-file-it-takes-too-long/2754
**Category:** ParaView Support
**Created:** [October 14, 2019, 9:53am UTC](https://discourse.paraview.org/t/paraview-saves-state-py-file-it-takes-too-long/2754 "2019-10-14T09:53:56Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![RisingYoung-Learn](https://discourse.paraview.org/user_avatar/discourse.paraview.org/risingyoung-learn/32/2096_2.png) [@RisingYoung-Learn](https://discourse.paraview.org/u/RisingYoung-Learn)
#### Post date: [October 14, 2019, 9:53am UTC](https://discourse.paraview.org/t/paraview-saves-state-py-file-it-takes-too-long/2754/1 "2019-10-14T09:53:56Z")

</div>

Hello,

I created 50 Cones in ParaView(ParaView-5.7.0-Windows-Python2.7-msvc2015-64bit), Save State as a pvsm file, which took about 1.7s, and saved as a py file, which took about 9.73s. As shown below:  
 ![image](https://discourse.paraview.org/uploads/default/original/2X/2/23d9c4661e498344a7a6c6679825cfdfbaab260b.png)

Tests show that if the number of Cone is larger, the difference between the two is greater! At this time, because when saving as a py file, you need Python and C++ to call each other, which is caused by low efficiency? Or is it because of the special handling of saving as a py file? If I need optimization, what can I do?

Thank you!