While this seems like a serious issue for you, and I'm sorry you're experiencing this, I still prefer that we focus on getting Dancer 2 out, and it will be easier to fix it on 2 than on 1.

Making sure this doesn't happen to you on Dancer 2 will be a good point to start. :)

On Tue, Oct 16, 2012 at 1:50 PM, Konstantin A. Pustovalov <lamoz@adriver.ru> wrote:
I have found that dancer's memory consumption is indeterminant.
I believe I have found the source of my problem here - https://github.com/sukria/Dancer/blob/devel/lib/Dancer/Request.pm#L381
_build_params copies all first-level keys of huge POSTed hashes into params (there must be some more places where data is copied as memory consumption is more than 2x). Being newbie dancer I am not sure about further investigation.
Is it a valid behavior? I think that only application/x-www-form-urlencoded should be copied or this behavior should be switchable perhaps.
Any ideas on how to live with that?




_______________________________________________
Dancer-users mailing list
Dancer-users@perldancer.org
http://www.backup-manager.org/cgi-bin/listinfo/dancer-users