Changing the number of records processed

Craig Phillips

Jan 18 |13:33 PM

Last Updated on Saturday, 10 December 2011 11:28

Background

If you have a table with a large number of fields in each record you may experience timeouts or out of memory problems. This occurs for a variety of reasons including PHP file upload limits, memory limits and time out settings.

If you've already tried

splitting the file up into smaller files and appending the records.
increasing the limits mentioned above

Then you could try modifying EasyTable Pro to process a smaller number of records at a time.

In EasyTable Pro you can change the "Chunk Size" setting by logging in as the Super Administrator and entering an new value — the default value is 50 rows at a time.

Depending on your record size you can safely reduce the value of $chunkSize to 1 if required, in most cases simply halving the value is sufficient.

This will do several things, one it will reduce the amount of memory required to process each chunk and two if will increase the number of steps required to process the same number of records, causing the process to take longer than it would normally.

For versions prior to EasyTable Pro 1.0.0ß1

To do this you will need to edit the file /administrator/components/com_easytablepro/controllers/easytable.php

In that file you will be looking for the following code "$chunkSize = 50" highlighted in the code block below:

function updateETTDTableFrom ($id, $ettdColumnAliass, $CSVFileArray)
{
// Setup basic variables
$hasHeaders = JRequest::getVar('CSVFileHasHeaders');
$totalCSVRows = count($CSVFileArray);
$chunkSize = 50; // Arbitrary chunking size at this point...
$csvRowCount = 0; // Check our CSV column count matches our ETTD

Current as at 9th June 2011.

RSForm!Pro is a powerful Joomla! form creator, helping you to create custom forms in minutes. The new product makes form management much easier and gives you the time to handle your clients better.

For only €19.00 how can you go wrong?
( We've used it for years... Shouldn't you? )