Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Convert-ASN1 CPAN distribution.

Report information
The Basics
Id: 6986
Status: resolved
Priority: 0/
Queue: Convert-ASN1

People
Owner: Nobody in particular
Requestors: salvejn+cpanbug [...] met.no
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 0.18
Fixed in: (no value)



Subject: Make Convert::ASN1::parser mod_perl-friendly
Convert::ASN1 0.18 perl v5.8.3 uname -a: Linux myhostname 2.4.19-50um #1 Tue Jan 27 10:48:40 GMT 2004 i686 GNU/Linux Using a clean and updated install of Debian testing (Sarge) ---------------------------------- I'm setting up a mod_perl server, running OpenInteract2, with LDAP in use. Having a look at what Apache::Status has to say about memory usage (using B::TerseSize, and enabling the StatusTerseSizeMainSummary and StatusTerseSize features) I notice that Convert::ASN1::parser and Convert::AS1 both are quite memory hungry: File::Find 2127256 bytes | 3630 OPs Convert::ASN1::parser 1218845 bytes | 3356 OPs File::Copy 657597 bytes | 2805 OPs Convert::ASN1 570976 bytes | 7701 OPs OpenInteract2::Action::Page 468196 bytes | 4991 OPs (I removed some of the B::* modules for clarity) Inspecting Convert::ASN1::parser, I find that the following methods are listed on top: yyparse 84342 bytes | 1859 OPs compile_one 22327 bytes | 514 OPs yylex 11147 bytes | 201 OPs verify 10008 bytes | 245 OPs expand_ops 8405 bytes | 181 OPs Can the Convert::ASN modules be made less memory intensive?