CreateFromDocument() takes upwards of 20 minutes to finish processing a 240 line xml document whose tree depth never exceeds 6. The function also seems to be a voracious consumer of memory, sucking down hundreds of megs during the course of its operation - this seemed fishy to me, so I thought I'd ask if I should be expecting any differently. Should I be?
Oh, Also:
I am running on a 3.6GHz machine with 3.5 GB of memory. The schema for which I have generated bindings can be found here: http://cse.unl.edu/~bkutsch/3_0_Final.xsd
Thanks for any assistance. Also, if this does turn out to be a bug, I will certainly submit a ticket.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just glancing at your xsd, I expect you're running into this one. If this seems plausible to you, please add a comment to that ticket, especially providing information on your need for a solution (importance to you and when you need a working solution). Fixing this won't take more than a day or two, but right now I'm caught up in real work for which I'm sorta getting paid, so that's taking priority.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Peter, I would like to ask about https://sourceforge.net/p/pyxb/tickets/66/ status. I can see that is scheduled for PyXB 2.0, but you already posted some significant improvements here. Do you have a patch for these changes?
Regards,
jaroslaw
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That was scheduled for 2.0 seven years ago. It didn't make the cut when unfinished but still potential tickets were transferred to Github over three years ago. There are no global performance improvements coming, and an API change away from properties is certainly not going to happen.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
CreateFromDocument() takes upwards of 20 minutes to finish processing a 240 line xml document whose tree depth never exceeds 6. The function also seems to be a voracious consumer of memory, sucking down hundreds of megs during the course of its operation - this seemed fishy to me, so I thought I'd ask if I should be expecting any differently. Should I be?
Oh, Also:
I am running on a 3.6GHz machine with 3.5 GB of memory. The schema for which I have generated bindings can be found here: http://cse.unl.edu/~bkutsch/3_0_Final.xsd
Thanks for any assistance. Also, if this does turn out to be a bug, I will certainly submit a ticket.
Just glancing at your xsd, I expect you're running into this one. If this seems plausible to you, please add a comment to that ticket, especially providing information on your need for a solution (importance to you and when you need a working solution). Fixing this won't take more than a day or two, but right now I'm caught up in real work for which I'm sorta getting paid, so that's taking priority.
Version 1.1.1:
Version 1.1.2:
I'm pretty happy.
Hi Peter, I would like to ask about https://sourceforge.net/p/pyxb/tickets/66/ status. I can see that is scheduled for PyXB 2.0, but you already posted some significant improvements here. Do you have a patch for these changes?
Regards,
jaroslaw
That was scheduled for 2.0 seven years ago. It didn't make the cut when unfinished but still potential tickets were transferred to Github over three years ago. There are no global performance improvements coming, and an API change away from properties is certainly not going to happen.