[geeklog-devel] Geeklog 2.0.0rc1 Bugs
cordiste
cordiste at free.fr
Fri Oct 5 14:04:31 EDT 2012
I would like to test PCNTL but PCNTL functions are not available all
my PHP installations :(
[code]
if (! function_exists('pcntl_fork')) die('PCNTL functions not
available on this PHP installation');
for ($x = 1; $x < 5; $x++) {
switch ($pid = pcntl_fork()) {
case -1:
// @fail
die('Fork failed');
break;
case 0:
// @child: Include() misbehaving code here
print "FORK: Child #{$x} preparing to nuke...n";
generate_fatal_error(); // Undefined function
break;
default:
// @parent
print "FORK: Parent, letting the child run amok...n";
pcntl_waitpid($pid, $status);
break;
}
}
print "Done! :^)nn";
[/code]
Ben
2012/10/5 Dan Stoner <danstoner at gmail.com>:
> I believe that Wordpress has some kind of "cron" system for doing this
> sort of thing, although I don't know the details of the
> implementation.
>
> - Dan Stoner
>
> On Fri, Oct 5, 2012 at 11:28 AM, Vincent Furia <vfuria at gmail.com> wrote:
>> I've never tried it with PHP, but we could fork (pcntl_fork) the Content
>> Syndication stuff so it doesn't impact the user viewing the page.
>> Regardless, we should not be running it on every page load.
>>
>> -Vinny
>>
>>
>> On Fri, Oct 5, 2012 at 5:51 AM, cordiste <cordiste at free.fr> wrote:
>>>
>>> Tom,
>>>
>>> How did you track the execution time?
>>>
>>> A solution could be to only update rss every hour. If we need more
>>> updates, we could recorde the last run time and check if story date is
>>> between now and this last run on pages where this article is display.
>>> If yes then we update the feed.
>>>
>>> Ben
>>>
>>> 2012/10/4 Tom <websitemaster at cogeco.net>:
>>> > Okay,
>>> >
>>> > I have been doing some speed tests and it looks like Content Syndication
>>> > is
>>> > taking about 50% of the execution time for creating the homepage on
>>> > Geeklog.net.
>>> >
>>> > On Geeklog.net we have 6 rss files. 4 are article related, 1 comment and
>>> > 1
>>> > forum. The main article and comment rss takes up the bulk of the
>>> > processing
>>> > time.
>>> >
>>> > Looking at the code I see that these files are checked to be updated
>>> > every
>>> > single time someone visits Geeklog.net/index.php
>>> >
>>> > The reason given is that Geeklog allows articles to be published in the
>>> > future and because of this, we need to check to see if we need to
>>> > rebuild
>>> > the RDF file in the case that any such articles have now been published.
>>> >
>>> > This is an expensive way to go about making sure the rss files are
>>> > updated.
>>> >
>>> > I have a few ideas on how to improve this ... but I would like to hear
>>> > some
>>> > other suggestions!
>>> >
>>> > Tom
>>> >
>>> >
>>> > -----Original Message-----
>>> > From: geeklog-devel-bounces at lists.geeklog.net
>>> > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom
>>> > Sent: October-04-12 11:41 AM
>>> > To: 'Geeklog Development'
>>> > Subject: Re: [geeklog-devel] Geeklog 2.0.0rc1 Bugs
>>> >
>>> > I updated Geeklog.net with a fix that should take care of the anonymous
>>> > users and topics not being tracked properly.
>>> >
>>> > Tom
>>> >
>>> > Note: This does not fix bug 1486
>>> >
>>> > -----Original Message-----
>>> > From: geeklog-devel-bounces at lists.geeklog.net
>>> > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom
>>> > Sent: October-03-12 9:06 AM
>>> > To: 'Geeklog Development'
>>> > Subject: [geeklog-devel] Geeklog 2.0.0rc1 Bugs
>>> >
>>> > One bug I noticed is that the anonymous users are not being tracked
>>> > properly
>>> > for some reason.
>>> >
>>> > http://project.geeklog.net/tracking/view.php?id=1487 (Default Topic for
>>> > Article with Multiple Topics is always Used for Anonymous Users)
>>> >
>>> > This also probably causes this bug since the session information seems
>>> > to be
>>> > getting lost:
>>> >
>>> > http://project.geeklog.net/tracking/view.php?id=1486 (Topic selection is
>>> > lost when trying to contribute a story as a Story Admin)
>>> >
>>> > Tom
>>> >
>>> >
>>> >
>>> > -----Original Message-----
>>> > From: geeklog-devel-bounces at lists.geeklog.net
>>> > [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Tom
>>> > Sent: October-02-12 2:51 PM
>>> > To: 'Geeklog Development'
>>> > Subject: [geeklog-devel] Geeklog.net and Geeklog 2.0.0rc1
>>> >
>>> > Hi All,
>>> >
>>> > I went ahead and released Geeklog 2.0.0rc1 today and updated Geeklog.net
>>> > to
>>> > the RC1.
>>> >
>>> > It took a while (backups, copying files, etc..) but I only had a few
>>> > small
>>> > hiccups that really just related to the commentfeed and forum plugin
>>> > updates.
>>> >
>>> > I also went ahead and switched over Geeklog.net to use the new Modern
>>> > Curve
>>> > theme.
>>> >
>>> > The topics are also now updated to the new structure that we defined in
>>> > the
>>> > Redesign wiki document.
>>> >
>>> > Besides fixing any bugs that crop up, one thing is apparent that we need
>>> > to
>>> > concentrate on fixing soon. The speed of the site has dropped a fair
>>> > bit.
>>> > This was expected to a certain extent because more complex sql
>>> > statements
>>> > are needed now since we have child topics and allow stories to display
>>> > in
>>> > multiple topics.
>>> >
>>> > Speed on the Geeklog.net server is slow today for some reason. With the
>>> > old
>>> > site I was seeing speeds on the homepage of roughly 1 to 3 seconds. (if
>>> > I
>>> > recall from before this was usually under a second)
>>> >
>>> > After upgrading to 2.0.0rc1 I am seeing speeds of roughly 1 to 6 seconds
>>> > (averaging around 3) on the homepage which sometimes spiked to 12
>>> > seconds
>>> > for some reason.
>>> >
>>> > Obviously we need to fix this through more optimized sql statements, new
>>> > indexes, etc.. so the more help the better! :-)
>>> >
>>> > Also if you notice anything out of wack on Geeklog.net post it on this
>>> > mailing list so we can get it fixed.
>>> >
>>> > I forgot to mention that the forum has been updated as well to work with
>>> > Geeklog 2.0.0. If you notice any issues with it please let us know. I
>>> > also
>>> > notice that when I enabled the upgraded forum on Geeklog.net that the
>>> > site
>>> > seemed to slow by a second or so. This indicates the forum could also
>>> > use a
>>> > bit of optimizing as well.
>>> >
>>> > Thanks
>>> >
>>> > Tom
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > geeklog-devel mailing list
>>> > geeklog-devel at lists.geeklog.net
>>> > http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>> >
>>> > _______________________________________________
>>> > geeklog-devel mailing list
>>> > geeklog-devel at lists.geeklog.net
>>> > http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>> >
>>> > _______________________________________________
>>> > geeklog-devel mailing list
>>> > geeklog-devel at lists.geeklog.net
>>> > http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>> >
>>> > _______________________________________________
>>> > geeklog-devel mailing list
>>> > geeklog-devel at lists.geeklog.net
>>> > http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>> >
>>> _______________________________________________
>>> geeklog-devel mailing list
>>> geeklog-devel at lists.geeklog.net
>>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>>
>>
>>
>> _______________________________________________
>> geeklog-devel mailing list
>> geeklog-devel at lists.geeklog.net
>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
More information about the geeklog-devel
mailing list