Question

I’m doing some integrations towards MS based web applications which forces me to fetch the data to my php application via SOAP which is fine.

I got the structure of a file system in an xml which I convert to an object. All documents have an ID and it’s path. To be able to place the documents in a tree view I’ve built some methods to calculate the documents whereabouts through the files and folder structure. This works fine until I started to try with large file lists.

What I need is a faster method (or way to do things) than a foreach loop.

The method below is the troublemaker.

/**
 * Find parent id based on path
 * @param array $documents
 * @param string $parentPath
 * @return int 
 */
private function getParentId($documents, $parentPath) {
    $parentId = 0;
    foreach ($documents as $document) {
        if ($parentPath == $document->ServerUrl) {
            $parentId = $document->ID;
            break;
        }
    }
    return $parentId;
}
// With 20 documents nested in different folders this method renders in 0.00033712387084961
// With 9000 documents nested in different folders it takes 60 seconds

The array sent to the object looks like this

Array
(
    [0] => testprojectDocumentLibraryObject Object
        (
            [ParentID] => 0
            [Level] => 1
            [ParentPath] => /Shared Documents
            [ID] => 163
            [GUID] => 505d70ea-51d7-4ef0-bf79-8e912553249e
            [DocIcon] => 
            [FileType] => 
            [Title] => Folder1
            [BaseName] => Folder1
            [LinkFilename] => Folder1
            [ContentType] => Folder
            [FileSizeDisplay] => 
            [_UIVersionString] => 1.0
            [ServerUrl] => /Shared Documents/Folder1
            [EncodedAbsUrl] => http://dev1.example.com/Shared%20Documents/Folder1
            [Created] => 2011-10-08 20:57:47
            [Modified] => 2011-10-08 20:57:47
            [ModifiedBy] => 
            [CreatedBy] => 
            [_ModerationStatus] => 0
            [WorkflowVersion] => 1
        )
...

A bit bigger example of the data array is available here
http://www.trikks.com/files/testprojectDocumentLibraryObject.txt

Thanks for any help!

=== UPDATE ===

To illustrate the time different stuff takes I’ve added this part.

1. Packet downloaded in 8.5031080245972 seconds
2. Packet decoded in 1.2838368415833 seconds
3. Packet unpacked in 0.051079988479614 seconds
4. List data organized in 3.8216209411621 seconds
5. Standard properties filled in 0.46236896514893 seconds
6. Custom properties filled in 40.856066942215 seconds
7. TOTAL: This page was created in 55.231353998184 seconds!

Now, this is a custom property action that im describing, the other stuff is already somewhat optimized. The data sent from the WCF service is compressed and encoded ratio 10:1 (like 10mb uncompressed : 1mb compressed).

The current priority is to optimize the custom properties part, where the getParentId method takes 99% of the execution time!

Answer 1

As usual this was a matter of programming design. And there are a few lessons to be learned from this.

In a file system the parent is always a folder, to speed up such a process in php you can put all the folders in a separate array with it’s corresponding ID as the key and search that array when you want to find the parent of a file, instead of searching the entire file structure array!

1. Packet downloaded in 6.9351849555969 seconds
2. Packet decoded in 1.2411289215088 seconds
3. Packet unpacked in 0.04874587059021 seconds
4. List data organized in 3.7993721961975 seconds
5. Standard properties filled in 0.4488160610199 seconds
6. Custom properties filled in 0.15889382362366 seconds
7. This page was created in 11.578738212585 seconds!

Compare the custom properties by the one from my original post

Cheers