On 17/10/2008, at 16.12, Scott Marlowe wrote:
On Fri, Oct 17, 2008 at 7:39 AM, Collin Kidder <[EMAIL PROTECTED]>
wrote:
I was going to stay out of this but I'll jump in and defend him.
The people
on this list are so pedantic, so sure that their way is the only
way that
they absolutely rain
with this. The list policy has
been debated adequately in the past. You are not going to change it.
It is probably going to come up again every once in a while, as long
as it's not changed, but I will respect your wishes.
--
Kind regards,
Mikkel Høgh <[EMAIL PROTECTED]>
sm
On 17/10/2008, at 14.01, Bill Moran wrote:
In response to "Mikkel Høgh" <[EMAIL PROTECTED]>:
On 17/10/2008, at 13.20, Bill Moran wrote:
In response to "Mikkel Høgh" <[EMAIL PROTECTED]>:
On 17/10/2008, at 12.24, Tomasz Ostrowski wrote:
But again, how ofte
On 17/10/2008, at 13.20, Bill Moran wrote:
In response to "Mikkel Høgh" <[EMAIL PROTECTED]>:
On 17/10/2008, at 12.24, Tomasz Ostrowski wrote:
But again, how often do you want to give a personal reply only? That
is a valid use-case, but I'd say amongst the hundreds of
On 17/10/2008, at 12.24, Tomasz Ostrowski wrote:
On 2008-10-17 12:13, Mikkel Høgh wrote:
You're supposed to use "Reply to all" if you want to reply to the
list.
Well, I think the most common use case for a mailing list is to reply
back to the list, isn't that the wh
On 17/10/2008, at 11.37, Tomasz Ostrowski wrote:
On 2008-10-16 23:17, Mikkel Høgh wrote:
P.S.: Why are e-mails from this list not sent with a Reply-To: header
of the lists e-mail-address?
Because it is dangerous - too easy to send to the list, when you
really
mean to send to one. Most e
On 16/10/2008, at 18.27, Scott Marlowe wrote:
On Thu, Oct 16, 2008 at 9:26 AM, Stephen Frost <[EMAIL PROTECTED]>
wrote:
* DelGurth ([EMAIL PROTECTED]) wrote:
Seems Tomasz linked to the wrong patch. The patch he meant was:
http://drupal.org/files/issues/drupal_lookup_path-6.x.patch.txt
That'
It's not only to avoid one query, but to avoid one query every time
drupal_lookup_path() is called (which is every time the system builds
a link, which can be dozens of time on a page).
So, I think it's probably a worthwhile tradeoff on MyISAM, because
such queries are fast there, and you p
On 14/10/2008, at 23.22, Merlin Moncure wrote:
On Tue, Oct 14, 2008 at 5:04 PM, Mikkel Høgh <[EMAIL PROTECTED]> wrote:
After disabling SSL for localhost, I ran the tests again, and the
performance gap is reduced to about 30%.
ok, now consider you are on a read only load, with lots (if
After disabling SSL for localhost, I ran the tests again, and the
performance gap is reduced to about 30%.
--
Kind regards,
Mikkel Høgh <[EMAIL PROTECTED]>
On 14/10/2008, at 21.17, Magnus Hagander wrote:
Mikkel Høgh wrote:
On 14/10/2008, at 20.23, Daniel Verite wrote:
What I've
On 14/10/2008, at 20.23, Daniel Verite wrote:
What I've noticed on drupal-6.4 with Ubuntu 8.04 is that the default
postgresql.conf has:
ssl=true
and since drupal doesn't allow connecting to pgsql with unix socket
paths [1], what you get by default is probably TCP + SSL encryption.
A crude tes
--
Med venlig hilsen,
Mikkel Høgh <[EMAIL PROTECTED]>
On 14/10/2008, at 17.28, Ang Chin Han wrote:
On Tue, Oct 14, 2008 at 10:05 PM, Martin Gainty
<[EMAIL PROTECTED]> wrote:
Yes, it's rather braindead. I'd rather not worry about why, but how'd
we make Dru
FORK)…
--
Kind regards,
Mikkel Høgh <[EMAIL PROTECTED]>
On 14/10/2008, at 18.44, Ivan Sergio Borgonovo wrote:
BTW I hope someone may find good use of this:
2xXeon HT CPU 3.20GHz (not dual core), 4Gb RAM, RAID 5 SCSI
* absolutely not tuned Apache
* absolutely not tuned Drupal with little
On 14/10/2008, at 16.05, Martin Gainty wrote:
> The benchmark is a mostly read-only Drupal site -- a few admins,
but a
> lot of readers. Drupal as a benchmark is skewed towards lots and
lots
> of small, simple queries, which MyISAM excels at. The long term fix
> ought to be to help the Drupal
On 14/10/2008, at 11.40, Ivan Sergio Borgonovo wrote:
On Mon, 13 Oct 2008 20:45:39 -0600
"Joshua Tolley" <[EMAIL PROTECTED]> wrote:
PostgreSQL ships with a very conservative default configuration
because (among other things, perhaps) 1) it's a configuration
that's very unlikely to fail miserab
wrote,
"Without a realistic test scenario and with no connection pooling and
with no performance tuning, I don't think you should make any
decisions right now about which is faster". My apologies.
--
Kind regards,
Mikkel Høgh <[EMAIL PROTECTED]>
On 13/10/2008, at 06.54, Steph
ow best to
configure PostgreSQL for Drupal, or can find a way to poke holes in my
analysis, I would love to hear your insights :)
The performance test results can be found on my blog:
http://mikkel.hoegh.org/blog/2008/drupal_database_performance_mysql_and_postgresql_compared
--
Kind regards,
M
17 matches
Mail list logo
