php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #43287 Unserialize is very slow
Submitted: 2007-11-14 06:05 UTC Modified: 2015-01-18 04:22 UTC
Votes:7
Avg. Score:4.6 ± 0.7
Reproduced:7 of 7 (100.0%)
Same Version:4 (57.1%)
Same OS:5 (71.4%)
From: k dot gorbunoff at gmail dot com Assigned:
Status: No Feedback Package: *General Issues
PHP Version: 5.2.5 OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: k dot gorbunoff at gmail dot com
New email:
PHP Version: OS:

 

 [2007-11-14 06:05 UTC] k dot gorbunoff at gmail dot com
Description:
------------
I'm using serialize()/unserialize() very active for storing/retrieving objects to/from memory (using memcached/xcache). The main problem is performance: unserialize() takes very much time and finally caching comes not very effective. This is not version-related problem, I'm expecting on all 4/5 versions. Unfortunately there is now way to share objects between PHP processes without serialize()/unserialize(). I just want draw your attention to made unserialize() faster... or create a way to share data between PHP processes without using serializing at all. I think optimizing unserialize() should be easier. Thank you.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2015-01-09 01:00 UTC] ajf@php.net
-Status: Open +Status: Feedback -Package: Feature/Change Request +Package: *General Issues
 [2015-01-09 01:00 UTC] ajf@php.net
Is this still an issue? json_decode() (for JSON-encoded data) may be faster as it doesn't need to check for references.
 [2015-01-18 04:22 UTC] php-bugs at lists dot php dot net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Wed Jun 26 17:01:31 2024 UTC