Hello, BrowserUK.

I see. Example XML is just 613KB.

Copying Twig object is terribly slow. I guess Data::Dumper or dclone of storable will not do any good, because it is just huge.

    for ( $someData->children_copy( 'managedObject') ){
        handle_managedObject($t, $_);
    }
[download]

    for ( $someData->children( 'managedObject') ){
        handle_managedObject($t, $_);
    }
[download]

my ($t, $element)=@_;

# create rewrite rules using Twig 
my %rewrite_rules =(
    q/name="name"/ => "some value",
);


#replace with regex
my $buffer=$element->sprint; #get plain text of element
for (keys %rewrite_rules){
    $buffer =~ s/ $_  (.*?)  >  .*?  (?=<)
                /${_} ${1} $rewrite_rules{$_}/sx;
}

#just print out without changing $element
print $fh $buffer;

I vaguely imagined rewriting managedObject sub using regex,

Given the size of the OPs target files -- 100MB -- I'd drop the use of XML parser entirely and process the file as text.

That statement is tantamount to blasphemy around here, but it would be quicker, simpler and would work. And nobody would think twice if the files weren't labeled "XML".

---

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP Neil Armstrong

Me too. :)

- tye        

Haha, that was good one. I tried mentioned replacement and it's under 2 minutes for 90MB XML file, so I would expect 0.5h for max data set. Thanks for hints!