Right now I am exporting the DataTable using your online services. I want to switch the export to our server. I have downloaded and unzipped the PHP packages for pdf and excel in the server root. I have used the below code to call:
$(‘Grid’).exportToPDF(); //old working code
$(‘Grid’).exportToPDF(“generate.php”); //new code
The file “generate.php” gets downloaded instead of the datatable. I am using Apache 2.2 through wamp server and a dll at server end.
While the datatable is getting exported in our own server, it is much slower than compared to export from your website. Tables with over 300 rows is taking around 90 sec to export to an excel. PDF export around 15 sec . Our server has 4 vCPUs and 8GB of ram and runs on Windows server 2008, apache2.2 and PHP 5.3.5. Do we need to tweak anything in the PHP ini files or Apache?
Thanks
Hi, I’m not quite sure why the performance difference is such huge. Default export server is very small instance ( 1 CPU, 512 Mb ), so in your case export must run much more faster.
By the way, default export service is Java based, but php version works with comparable performance.
Thanks for your reply. We shifted the export to our server because of security concerns by a large customer. I have increased the memory limit in PHP ini file to 1028MB with no effect. My DataTable contains only 7 columns and 500 rows of data. It actually takes only 3 secs to display via SQL but the Excel export via PHP in our server takes close to 90 sec. Can you please duplicate a table of this type and check it out the PHP generator at your end?
The export is mostly server side functionality so version of client side lib doesn’t matter.
If you think that problem is caused by export code, please provide some example of dataset for which performance issue occurs. As similar dataset works much faster locally, problem most probably is not related to the data but related to the server’s configuration
thanks for your reply. The dataset is a treeview grouped over the first column. I am pasting the partial exported table below. The full table has around 500 rows.
Thank you for trying this out at your end. As you suggested, maybe it is our Apache server 2.2 configuration. Can you please recommend the correct configuration?