Export-Clixml Performance Issues


i have data collection script pulls information multiple data sources (mainly ad) , builds arrays of custom psobjects.  once have information stored in variables, use export-clixml create xml files can later import , report on using powershell.  this seems work quite smaller collection (500-2500), seems perform badly large collections (5000+).

so, there variable data limitations should aware of?  are there specific limitations should aware of when using export-clixml?  should consider building custom xml documents address issue?

note:  i cannot switch use export-csv because many properties in custom psobjects have multiple values.

suggestions?


~fr3dd

based on date of when module created (aug 2011), v2 compatible module json possible use.

http://poshcode.org/2930


boe prox
blog | twitter
poshwsus | poshpaig | poshchat | posheventui
powershell deep dives book



Windows Server  >  Windows PowerShell



Comments

Popular posts from this blog

Generating Event ID 91, 44 with CA (In Event Viewer with source as Certsvc)

Group policy default policy cannot be edited because network name not found

Problem when changing update source