headers
Justin Tadlock | 1 Feb 21:16

Re: 10K Users?

10K users isn't too many.  I've worked on sites with 50K users on 
$6/month shared hosting.  Just having a lot of users shouldn't be an 
issue with loading.

On 1/31/2012 1:02 PM, Justin W Hall wrote:
> I have a situation where I need to register premium users, collect basic information Name, number, etc,
provide a password. Was originally thinking of keeping all within WP by using S2Member or similar, but
I've never worked with an installation with quite so many users and am concerned about it handling the load.
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers <at> lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
Permalink | Reply | 4 comments |
headers
Rafael Ehlers | 1 Feb 04:37
Picon
Gravatar

Re: 10K Users?

This kind of problem came to me, in my last project, where we have 175K
users and 55 usermeta for each user, THAT is problem, because you can't
even access the wp-admin, we haven't figured yet why.
Maybe because WP is making some kind of caching on this usermeta, don't
know yet.

But still, the site (user end) runs smoothly! It's kind of impressive!

On Tue, Jan 31, 2012 at 8:47 PM, John Blackbourn
<johnbillion+wp <at> gmail.com>wrote:

> On 31 January 2012 21:29, Alex Hempton-Smith <hempsworth <at> gmail.com> wrote:
> > I'm in a similar position. But my concern is more about the number of
> > usermeta rows I'll be adding.
> >
> > For each user I've got at least 15extra fields of data I need to store
> > (some boolean, some text).
>
> If you have 10,000 users you're still only talking about 150,000 rows
> which is nothing. If you're on cheap hosting then you'll run into
> concurrency problems (the number of simultaneous requests MySQL can
> handle) long before you'll run into speed problems.
> _______________________________________________
> wp-hackers mailing list
> wp-hackers <at> lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
Permalink | Reply | 1 comment |
headers
Otto | 1 Feb 05:23
Favicon
Gravatar

Re: DOING_AJAX all the time

On Tue, Jan 31, 2012 at 5:30 PM, Steve Taylor <steve <at> sltaylor.co.uk> wrote:
> Duh - thanks!
>
> I always used to think that was a dodgy behaviour for constants (to
> return true when not defined). Then I forgot about it and they bit me
> again....

They don't return true when undefined, actually; they return strings.
It's just PHP making assumptions for you again.

Any undefined constant used like that is assumed to actually be an
unquoted static string. If you turn PHP Notices and error reporting
on, you'll see a message like this:

Notice:  Use of undefined constant WHATEVER - assumed 'WHATEVER' in
script.php on line 123

Basically it's evaluating that constant as the string instead. And any
string except the empty string is equivalent to "true" when used as a
boolean expression. So, there you go.

-Otto
Permalink | Reply | 1 comment |
headers
Otto | 1 Feb 05:31
Favicon
Gravatar

Re: 10K Users?

On Tue, Jan 31, 2012 at 9:37 PM, Rafael Ehlers <rafaehlers <at> gmail.com> wrote:
> This kind of problem came to me, in my last project, where we have 175K
> users and 55 usermeta for each user, THAT is problem, because you can't
> even access the wp-admin, we haven't figured yet why.
> Maybe because WP is making some kind of caching on this usermeta, don't
> know yet.
>
> But still, the site (user end) runs smoothly! It's kind of impressive!

It's unlikely to be an issue with the users table or the number of
users or even the number of meta. WordPress.org has a tad under 3
million registered users, with something like 20 million rows of meta
on the main usermeta table and dozens of other similar tables for
various things. Now, this is mirrored across a bunch of separate
database servers, but it scales fine.

The number of rows or size of your tables is rarely the main problem.
MySQL scales quite well in that respect, as do all other modern
databases. The real scaling problems lie in concurrency. The database
can be as big as creation and still serve things lightning fast thanks
to indexing, but even small databases will choke when you start making
thousands of requests per second to them.

If you're unable to load the back end at all, then it's unlikely to be
a table holding a mere few million rows that is the problem. Databases
with *billions* of rows can easily be made and will generally work
fine. Instead, it's more likely that you have a misbehaving
plugin/theme or other form of code causing the system to choke.

-Otto
(Continue reading)

Permalink | Reply | 0 comments |
headers
john malc | 1 Feb 15:18
Picon

Re: Easy-Hacks for WP

After reading this, I decided NOT to do this project. But still, one day, I
would like to have it.

2012/1/31 Stas Sușcov <stas <at> nerd.ro>

> În data de Tue, 31 Jan 2012 21:23:22 +0200, Jesper Jarlskov <
> jesper <at> jarlskov.dk> a scris:
>
>
>  I have on several occasions talked to the people behind the Linux
>> distribution Exherbo[0]. They have had great success getting new
>> contributors onto the project by keeping a bunch of low hanging fruits
>> around. This is stuff that is not critical, ie not security issues and so
>> on, but small easy to grasp usually nice-to-have features, that could
>> easily be fixed by the core developers. They make sure to always keep some
>> of these issues around to give aspiring contributors an easy way to get
>> started on contributing.
>>
>> I really like this idea and I know, as mentioned, that other projects has
>> had great success with it. I think one of the biggest problems to getting
>> new contributors on a project is that first commit.
>>
>> [0] http://exherbo.org/
>>
>> Jesper Jarlskov
>>
>>
>> On Tue, Jan 31, 2012 at 8:11 PM, Chris Williams <chris <at> clwill.com> wrote:
>>
>>  IMHO, the last thing a relatively mature codebase like WP needs is people
(Continue reading)

Permalink | Reply | 0 comments |
headers
Steve Taylor | 1 Feb 21:40
Picon
Favicon
Gravatar

Re: DOING_AJAX all the time

Well I'll be... Thanks for the info Otto!

On 1 February 2012 04:23, Otto <otto <at> ottodestruct.com> wrote:
> On Tue, Jan 31, 2012 at 5:30 PM, Steve Taylor <steve <at> sltaylor.co.uk> wrote:
>> Duh - thanks!
>>
>> I always used to think that was a dodgy behaviour for constants (to
>> return true when not defined). Then I forgot about it and they bit me
>> again....
>
> They don't return true when undefined, actually; they return strings.
> It's just PHP making assumptions for you again.
>
> Any undefined constant used like that is assumed to actually be an
> unquoted static string. If you turn PHP Notices and error reporting
> on, you'll see a message like this:
>
> Notice:  Use of undefined constant WHATEVER - assumed 'WHATEVER' in
> script.php on line 123
>
> Basically it's evaluating that constant as the string instead. And any
> string except the empty string is equivalent to "true" when used as a
> boolean expression. So, there you go.
>
> -Otto
> _______________________________________________
> wp-hackers mailing list
> wp-hackers <at> lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bryan Wright | 2 Feb 16:44

Problems setting publication date with newPost and perl WordPress::XMLRPC

Hi folks,

     I'm trying to use Leo Charre's WordPress::XMLRPC perl module to create new
posts that have publication dates in the past.  (I'm going to import some old
posts.)  Everything works fine except setting the publication date.  No matter
what I do, the publication date is always now, instead of the date I specify. 
Here's an excerpt from the code:

use WordPress::XMLRPC

my $postid = $wprpc->newPost({
    title       => $title,
    description => $body,
    pubDate     => $gmtisodate,
    categories  => ["News"]
                             });

I've tried several different date formats, and they're all accepted without
complaint, but the results are the same.

     Any advice would be appreciated.

                                               Thanks,
                                               Bryan
Permalink | Reply | 1 comment |
headers
Otto | 2 Feb 18:55
Favicon
Gravatar

Re: Problems setting publication date with newPost and perl WordPress::XMLRPC

Not sure why you're using pubDate in that struct. I think you should
be using something more like this:

dateCreated => '20080121T12:38:30',
date_created_gmt => '20080121T20:38:30',

-Otto

On Thu, Feb 2, 2012 at 9:44 AM, Bryan Wright
<bkw1a <at> ayesha.phys.virginia.edu> wrote:
> Hi folks,
>
>     I'm trying to use Leo Charre's WordPress::XMLRPC perl module to create new
> posts that have publication dates in the past.  (I'm going to import some old
> posts.)  Everything works fine except setting the publication date.  No matter
> what I do, the publication date is always now, instead of the date I specify.
> Here's an excerpt from the code:
>
> use WordPress::XMLRPC
>
> my $postid = $wprpc->newPost({
>    title       => $title,
>    description => $body,
>    pubDate     => $gmtisodate,
>    categories  => ["News"]
>                             });
>
> I've tried several different date formats, and they're all accepted without
> complaint, but the results are the same.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Diana K. Cury | 4 Feb 01:44
Picon
Gravatar

New image sizes for old files

I know how to add new image with add_image_size and use them, that is ok, but how to rebuild the images sent
before the new size?! 

Thanks,
Permalink | Reply | 3 comments |
headers
Charles Frees-Melvin | 4 Feb 00:39
Gravatar

Re: New image sizes for old files

I used this but it is best to deactivate it after you finish converting. 
http://wordpress.org/extend/plugins/ajax-thumbnail-rebuild/ 
--
Charles E. Frees-Melvin

Sent from my Rogers iPhone 4S

On 2012-02-03, at 20:44, "Diana K. Cury" <dianakac <at> gmail.com> wrote:

> I know how to add new image with add_image_size and use them, that is ok, but how to rebuild the images sent
before the new size?! 
> 
> Thanks,
> 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers <at> lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
Permalink | Reply | 0 comments |

Gmane