WordPress 3.2 and Development BackWPUp

  • I picked up the development version yesterday to test against WP 3.2 RC2. Overall, it works well. However, I did notice a couple of things. One, I can’t delete the ‘New’ job. I can delete any new ones I’ve created. Second, I noticed cpu utilization on one of the apache2 processes mostly between 40-60% with occasional spikes to 400%. The job was dbase backup and file backup. The number of files included in the backup were 3923 and took 385 seconds.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter RobIrizarry

    (@robirizarry)

    For comparison, I ran a similar job for a different site on the same virtual private server. This site runs WP 3.1.3 and BackWPup ver 1.7.7. The backup contained 3690 files, resulted in an archive of 128mb (vs. only 21mb for the run performed above with the development version) and took 126 (vs. 385) seconds as per the job’s log files. This job barely blipped the cpu which bounced between 20-30% during its run.

    That’s dramatically better than the development version’s results indicated above.

    hmmm… the development version works with sessions and writing offten a runnig file. it make more on the filesystem. i will look to reduce it.

    did you have look in the arcives whre the size cange comes from ?

    If have implementet a preformance reduce for the backup prozess.
    But i have only hiher peack if i show the backup working. if it woks in backround i can’t see it.
    pleace download the development verion again i will lokk to reduce the forceground working.

    it me again i have now improft the show working prefomance too please test agin and give feadback.

    Thread Starter RobIrizarry

    (@robirizarry)

    Thanks for the feedback.

    The two jobs were different in size due to the size of the environments. The smaller zip was on a test environment with only a handful of images. The larger zip was on a prod environment with gobs of images and a number of pdfs. Despite the greater size of the prod environment, the plugin log files indicate that the 1.7.7 version blew through the entire process in less than 1/2 the time.

    I’ll pull down the latest plugin version, test again and provide feedback.

    Thanks again.

    Hi,
    Loving the plug-in and the new dev version, but are there any plans to add the option to change the temporary folder? This is crucial for me!

    If not, would you be able to tell me how to hardcode a different directory in?

    Thanks
    Jon

    why is it crucial ?

    The site I’m working on doesn’t have access to the tmp folder which the plugin uses.
    Jon

    ok i will try to make a extra file in the plugin folder wher u can place the tmp folder.

    that is the only way.

    ok now you can lace a .backwpuptempfolder file in plugins folder with the tmp path in. Than this path will taken.

    Thanks Daniel,
    Although I’m not sure what you mean exactly – can you show me an example of that file?

    Thanks
    Jon

    a example is in the readme.txt put only the folder nome in the file nothing else…

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘WordPress 3.2 and Development BackWPUp’ is closed to new replies.