StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17073663
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-12T19:26:35.073
FavoriteCount
0
LastActivityDate
2013-06-12T19:26:35.073
LastEditDate
LastEditorUserId
0
OwnerUserId
336311
ParentId
16750481
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The solution found on <a href="http://we-love-php.blogspot.de/2012/06/php-memory-consumption-with-arrays.html" rel="nofollow">http://we-love-php.blogspot.de/2012/06/php-memory-consumption-with-arrays.html</a> actually proved very helpful. I think it is worth, posting here: <blockquote> The most efficient kind of an array in PHP is a string. </blockquote> Actually storing a large number of integer values within a string (4 bytes or characters for each integer) saves more than 80% (!) of memory. Of course there are lot of disadvantages: You need to encode/decode the integers, sorting requires custom functions, etc. Therefore, this solution is only sensible when memory really matters. In my case, 16-bit integers were sufficient, so I could encode each integer with 2 characters. Here is the sample code I employed: <pre><code>private function retrieveReferences() { $query = $this->getResultsQuery(true); $timesSE = array(); $tp = -1; // Length of $times - 1 while ($row = $query->fetchArray()) { $timeSrc = explode(',', $row['times']); // Store the times per page foreach ($timeSrc as $p=>$s) { // Should be faster than checking isset $times[$p] all the time while ($p > $tp) { $timesSE[] = ''; $tp = count($timesSE) - 1; } // Save to limit to 16bit (in this specific case) $i = (int)$s; if ($i > 0xFFFF) { $i = 0xFFFF; } $timesSE[$p].= chr(($i & 0xFF00) >> 8).chr($i & 0x00FF); } } // Compute median for each $times[$p] // <snip> } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMemory-efficient data structure for matrix in PHP
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBurninLeo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.