Here are some test results using a microtime function i setup
Using database
0.77256107330322 seconds
Using cache
0.23316502571106 seconds
My next problemo is, i have built a Date and Calender class to build the
date and time pulldown's. Although it seems really slow, i have to tweak it
someho
Here is my final layout, i still yet to test it on the production machine
being a dual 2G xeon, has had major performance issues generated list menus
onto the screen and load time.
function asset_type_list2($tID=null,$tab_index = null,$cache_data =
null,$disabled = null) {
global $
The code works, and seems to run pretty fast, another question would
storing in xml be a better option ?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
I havent tested this yet, it seems it may be more harmful than good ?
if ($cache_data) {
$query = $db->query("SELECT cache_data FROM
cache_menu_table WHERE table='foo'");
if ($db->results()) {
$query = "SELECT cache_
> It's not really that bad, maybe I just made it sound complicated and
> annoying.
>
> (pseudo-php)
>
> If (dataexistsindb) {
>$cachedata = SELECT cachedata from DB
>$dataarr = unserialize(cachedata)
> } else {
>$dataarr = SELECT freshdata
>$cachedata = serialize($dataarr)
>INSE
It's not really that bad, maybe I just made it sound complicated and
annoying.
(pseudo-php)
If (dataexistsindb) {
$cachedata = SELECT cachedata from DB
$dataarr = unserialize(cachedata)
} else {
$dataarr = SELECT freshdata
$cachedata = serialize($dataarr)
INSERT or UPDATE $cac
Unfortunately not even SQL_CACHE works in this scenario, with 5 or more
generated menus, its a noticable difference in load time.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
> $_SESSION sounds like a good way to go.. It just means that each user
> will pull the data for the menu at least once.
>
> I've done something similar except it was a rather slow database query,
> followed by a bunch of conditional data parsing. The end result wasn't
> very much data (maybe a p
$_SESSION sounds like a good way to go.. It just means that each user
will pull the data for the menu at least once.
I've done something similar except it was a rather slow database query,
followed by a bunch of conditional data parsing. The end result wasn't
very much data (maybe a page's worth
9 matches
Mail list logo
