Shared Memory and PHP

Question

0.00/5 (No votes)

See more:

Please how can shared memory be created in PHP using shmop_* (not shm_* if that matters) be locked and unlocked? Does this require libraries?

It seems shmop_read() runs while shmop_write() is still writing because the value read has part of old and new values.

This is the situation, there are three sections. Section One open/create the shared memory segment and write/update it content. Section Two update what is already written into the segment while the Section Three read what is in the segment. Any of these sections can run at any time.

Posted 29-Apr-13 22:26pm

Oso Oluwafemi Ebenezer

Updated 29-Apr-13 22:28pm

v2

Add a Solution

Comments

Mohibur Rashid 30-Apr-13 5:06am

Why do you want to do that?

Oso Oluwafemi Ebenezer 30-Apr-13 5:22am

Because am using the shared memory to monitor some user interactions and while reading content out of the segment, any user may perform any action that necessitate writing to the segment which will result in the situation I describe above.

Mohibur Rashid 30-Apr-13 5:57am

I would suggest you think other way, may be database

Oso Oluwafemi Ebenezer 30-Apr-13 6:07am

Database is out of the question because of heavy connection which database can't handle. Say 30k users at the same time!

Prasad Khandekar 30-Apr-13 6:44am

Why not use an in memory database?

Oso Oluwafemi Ebenezer 30-Apr-13 7:07am

Connection overload will still be an issue

Prasad Khandekar 30-Apr-13 8:22am

Please have a look at memcached. It might be useful for you.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)