User talk:Replysixty - Knowledge (XXG)

688:

clear NPOV criticism of Drupal's performance or scalability-- it referred to a single issue (caching) without much explanation of (1) what caching is, (2) how it relates to performance/scalability, and (3) aside from a direct comparison to a single other CMS only in terms of caching, any criticism of Drupal's overall performance and scalability. It was just a bunch of technical babble with a single metric and a single competitor (against whom it performed relatively favorably- in its worst test it served 13 pages to Joomla's 19, in all other tests it smoked Joomla) . It was NPOV because it was framing an article (by the lead developer, no less) giving a positive cache benchmark as a negative criticism without any logical connection between one and the other. (Not to mention offering a basic description or primer of how this "caching" thing relates to performance and scalability) --

1359:

corporation" or "A conference of CMS administrators voted this a major hurdle Drupal needs to overcome" or something like "this issue is unique to Drupal" or "this is a common issue with all CMSs, but advancements in database access technologies including xy, and z make it likely to be a non-issue in the future" or SOMETHING to indicate that this DOES belong in a criticism section. Ideally, technical terms like "modular design" or "computational overhead" or "page rendering" or "caching" would be linked to the appropriate wikipedia article. My big question though is-- is this a notable criticism of Drupal? Where are the big corporations that have had scalability and performance issues? If someone at a conference gave a speech saying "this is why drupal sucks..." that would be a big help to say, yeah this is a real thing, as opposed to "oh this

2506:

first-hand experiences get referenced on Knowledge (XXG) to an article: They get quickly removed and replaced by links to CNN and AP, because those are more "authoritative", but what's happened is now the accounts are less true, less direct. We're accepting more vague, third-party references because we're supposed to trust the source more. Now like I said, personal opinion, but I'd rate your actual experiences higher than a magazine which is more interested in public image like betting on a horse. Knowledge (XXG) has migrated this way because it has attracted a lot of abuse on articles, but it's a shame just the same that typically the respected references are IMHO the wrong ones. I can't change that and I'm not trying to here, but just being brutally honest about it.

1684:

no idea. The point is that while the discussion is interesting, it still feels like speculation to me... If you started with a conclusion: "Users agree: Drupal is slow and these benchmarks show it is slow relative to 5 other CMSs" and then explored reasons for the slowdown, including more SQL requests, that would make sense and probably should go in the article. But to start with "Drupal is modular, modular means more SQL requests, more SQL requests must mean drupal is slow..." I don't know.. --

2334:

lack of a focus statement for the software is notable, even the top paragraph cannot decide whether Drupal is a CMS or Framework or something else. I know they haven't clarified these focuses within the Drupal community, but the Knowledge (XXG) entry could at least indicate target audiences and limitations of using Drupal outside of that scope. That's where the criticisms come into play, because in this case they're defining Drupal as much as the rest of the article is.

548:. The entire Criticism section suffers from having no real sources, I couldn't find to much myself in a quick search, but any good source that can be found criticizing Drupal would be great. If Novasource can write a NPOV criticism backed up by sources, then that has every right to stay in the article, but I don't think that has happened, and what Replysixty is trying to keep in the article is more accurate than Novasource's additions. Replysixty's replies to your 2884: 445: 4138: 4050: 3896: 3821: 3725: 3652: 2792: 2586:

software or switch designs. He was asking how much scaling anyone thought he might need so he could price it and just like this situation, nobody knew because benchmarks in scaling situations just don't exist. Now, the reason I tell this, is that we don't need the same info he did, we don't need detailed benchmarks, but simply that the issue exists, that it does limit the software's usage / choices.

2702:

discussion. IMHO, to be notable, the criticism should represent a consensus opinion or a critique by an authority. So if we're talking about performance issues, I need evidence that this is truly and fairly an issue for Drupal- and I'd like context-- comparison with other CMSs, a discussion of some structural or design flaw, the impact the problem has, and even any proposed solutions... --

3799:, I'm not sure if it would notify you automatically so I thought I would leave you a note here on your talk page as well. I'm interesting in this list because I am teaching a research methods course and am working with students to better understand science communication and making connections to people in popular culture (mass media) who they already recognize would help in this effort. -- 705:-- The article was chosen and is in reference to Drupal's caching affecting static content and not reflective of Drupal's actual perfomance, which Dries Buyart does address. You're trying to say it doesn't apply to the whole section of performance, but it was specific to that aspect. Go read it again, I'm not going to cut-and-paste a section like you've done, you can just read it. :P 3190: 1416:

slower than a Drupal system where only 1 of 15 modules are turned on, right? Speaking for myself- I don't use many of the core modules- they're not even checked in the Modules section. This means the tables are never created, the code is never loaded into memory or run. So maybe there is a performance advantage as well as penalty for modules, depending on which are used...? --

684:

tasks". Okay, great. But aside from the confusing sentence structure, does this have any meaning to a casual non-technical reader? How many buzzwords can you fit into two sentences ("primary optimization", "dynamic environments", "interactive tasks", etc. etc.) ? And is it in any way "criticism"?! Doesn't seem like it to me-- It's just a vague comment on speedup mechanisms.

3038: 461: 3354: 1758:

there and Drupal is 2nd place to it (this is made up, but I'm just saying...) does this mean Drupal is slow? What is the context compared with other CMSs or with actual administrators' usage? I can say that a Honda Civic has a slower top speed than a Corolla, but does that mean that a common criticism of the Civic is that it has poor performance? --

2213:

criticism. But while there are zillions of people who may have this or that issue, I think the section "Criticism" should be for widely acknowledged and notable issues with Drupal behavior/licensing/cost/utility/etc., not simply a place to discuss an issue that any single person may be having. It should also easy for a lay person to understand. --

425: 368: 869:. I did not want to say that "Drupal provides a seamless upgrade path for the end user" because some users may have trouble with migrating their sites to new versions. So I said "strives to". I could have said "aspires to" "has a policy to" "tries to" etc. I said "strives"... I don't think that's very advertisey, but whatever. Change it. -- 2032:

their own database requests independent of each other. These independent database queries take more time and could result in slower page generation. On the other hand, a modular design allows administrators to turn off features they do not use, which may end up saving database queries when compared to a similar non-modular CMS. Also,

215: 1245:

caching and reduce modules, but the entire modular nature is designed for, well-- modules and interactive sessions that don't cache (not the overall caching system at least). So to get the impressive performance in the benchmarks, the site has to deliver content much different than the goals of most Drupal sites.

2585:

Back to the scaling again, I wish I still had the link and maybe I'll hunt it down, but a perfect example was a cartoonist website that dynamically displayed his strips and as such the caching was useless and very quickly his server reached its limits. He had to decide whether to scale higher, switch

2428:

FWIW, I do know at least one person who does use Drupal as a personal blog. I have no clue what "typical usage" is-- whether it's corporate, personal, hobbyists, bloggers... don't know. It could be any of those things.. but if you have the data, I'd say put it up there, because you're right-- it is

1757:

But (1) the Dries article is three years old, (2) it says that Drupal is slower than Joomla w/o caching in handling 14 rather than 19 requests (something like that I don't have it in front of me), and (3) again, I don't know that it constitutes a notable criticism... if Joomla is the fastest CMS out

1304:

One problem with sourcing is that people who've run into these problems jump to other software rather than try to swim upstream fixing it, but that's why I'd like to see it in the article, because it's not well addressed. Perhaps this makes Knowledge (XXG) the wrong venue, but I'm honestly not trying

1131:

If you do have a vested interest, please have some sanity and understand the notion of recusing yourself. I will refrain myself from editing because I have zero interest in some Knowledge (XXG) war with you. I did undo your gigantic deletion of the work I added, I hope you gain some clarity to either

1096:

If there were one more criticism I'd apply to Drupal it's that the community has too many watchdogs like yourself that are so interested in protecting Drupal's image as respected software, that it doesn't grow or improve as much as it should. The flaws are too well defended and excused for, again, by

971:

Because it was so poorly written as described above, I felt the article was more accurate without the section. There are other criticisms which I think are valid and supported and I have contributed to those sections. The criticism you added was nonsensical and baseless enough to me that POV seemed

495:

is a disgruntled editor who is crying "vandalism" because he does not like me reving out his POV and OR. Rather than citing a valid reference in his edits, he chooses to universalize his own opinions and inject them into the article as objective (and notable) fact. Anyone who might be interested in

2542:

everyone posting their subjective experiences on every topic. In other words, you may be in some ways the best person to write an entry about yourself. But in many ways you are the worst person to do so. I understand for an encyclopedia why WP asks you not to do this, and I think the same sort of

2110:

See above. In your example though, you'd need a citation more to indicate that the lack of image support exists, but that it's a problem. Ie, an article in CMS Weekly called "Drupal's Image Handling SUCKS!!!!" would be a better citation than just linking to the ImageCache module or whatever if the

1800:

The Drupal 7 notes also document that they're reducing SQL queries, indicating it's still an issue. Why does it have a 2006 disclaimer in there that steers away from the inherent conclusion and reads like it's a problem in the past? It isn't, it's exactly as it was until Drupal 7 comes out (and then

1683:

Except that this may be a totally negligible performance hit in real-world terms. Or it may be that Drupal has optimized the way it handles module database calls in some interesting way-- perhaps all modules calls are cached, optimized, and then run in a single database access by the API... I have

1612:

from a modular design, are we just speculating here as far as Drupal vs. other modules? Or is it an established fact that most other CMSs may have a module or two turned on? If so, which modules, and what is the cited source? Benchmarked comparisons would be very helpful. Then, assuming that the

1415:

Are you sure about this? Do other CMS' not modularize their core functions? Also, couldn't the modular design be a performance ADVANTAGE, because it easily allows admins to restrict Drupal to only those modules they want? For example, a system with 15 hard-coded functions would be much larger and

724:

I have read the article several times now. I am not saying that caching is unrelated to performance. I am saying that the section did not read well and did not make a clear connection from "Performance & Scalability" to a bunch of stuff about caching and comparison to Joomla. Is Joomla fast?

679:

Uh, no. The article (which I did actually *READ*, and yes I know it's by Buyart) showed that when caching was on, and I quote from the article, "Joomla's cache system improves performance by 12%, while Drupal's cache system improves performance by 508%." Even though Buyart concedes it may not be a

3530:

Wow. Okay, umm. I'm just gonna keep doing my editing thing, and if you spot an issue let me know. Funny cuz I didn't feel like I was in any kind of edit war situation or even in contention with anything that had been edited between my edits-- I simply took a break and came back a few hours later

2188:

I don't know if I agree that the references need to indicate repercussions, just indicating that the issues exist and they concern both users and potential users. It's not that it isn't a problem, it's that as a problem it acts as a filter and barrier for who's likely to implement the software into

1951:

We're oversaturating references. The citations are getting excessive on things that are clearly true. This leads back to my original beef, because AFAIK Knowledge (XXG) policy for well-referenced articles doesn't equate to requiring a reference on every statement, or else immediate deletion. That's

1545:

But what about the point that drupal's modularity allows admins to NOT include/load certain modules that would otherwise be loaded by a rival CMS? Doesn't this promote a MORE efficient use of resources when compared with a CMS that throws in everything (including the kitchen sink)? A CMS with the

1344:

access for more efficient and scalable page rendering. One proposed solution to this issue is Drupal's core caching system, which stores static pages, reducing the need to re-generate them. Unfortunately, static pages are used mostly by anonymous visitors, so logged in users will not receive much

1300:

I'm stating it this way above so you have a better idea of what the actual criticism is that I'm trying to convey. I'm not suggesting it should be written into the article verbatim, it's too long for the subject matter and not reference sourced (although it could be from just one or two references,

1254:

Arguably, any site on any software could match that exact performance with the addition of a site-wide cache because at that point it's just delivering static pages. Anyone sending out static pages probably shouldn't be using Drupal, there are other CMS systems better suited for that environment or

1108:

You're making a lot of wild assumptions about me and my motivations. My motivation is only a complete and well-written article. Sounds like you have a serious chip on your shoulder, which again suggests a lack of NPOV. And by the way, where the hell did I "defend" or "excuse" any flaw in Drupal?

936:

I am a (non-professional) Drupal user. (I have in the past used many other CMSs over more than a decade, so I have some familiarity with the topic), but would not say I have a particular POV interest. My problem with your addition was that to me it was not supported by the cited article, was very

687:

I don't see how anything I added constitutes "glowing praise". I did reorganize a section on "learning curve" which had nothing to do with learning curve (but rather ease-of-use, which was covered in the previous section.) And I got rid of the Performance/Scalability section which did not provide

661:

Criticism sections should include criticism, balanced with unbiased reasoning, not glowing praise. Stop whitewashing please. Stop deleting. Your comments claimed you were editing for POV, but have extreme POV edits! You removed a citation without actually reading it, you assumed with the title that

2701:

I don't worry about the negativity-- a criticism section will by its nature discuss "negative" aspects of Drupal. I just want whatever is there to pass the tests of being notable, easily understood, accurate, and well-supported by objective citations. It has to be more than simply an interesting

2537:

I can't account for wikipedia's reasoning over citing sources- I guess it's just preferred to have at least a single person's distance between the article's subject and the article itself. There are inherent flaws in this (you can still write an article somewhere and then publish it as a source),

2333:

On the topic of big corporations having scalability and performance issues, I think that's the part that's notable, that Drupal is more designed with those in mind and (in this issue at least) not as appropriate for users without scaling options (shared hosting for example, or limited budget). The

2080:

As an example: If you say that most CMS' have a way to insert and display images by default but for Drupal you need a third-party module, that's just true and there's unlikely any argument against it, so why does it need a citation? If there was a dispute or confusion, sure, but I've never heard a

2031:

Drupal's plug-in modularity is intended to offer the system flexibility in features and functionality. However, this design may have a performance cost when compared to non-modular CMSs. For example- a non-modular CMS may optimize its database calls whereas modular components of Drupal each make

1584:

That's exasperated by the popular Views, CCK and related modules. Hugely different from say, a module in any other CMS that inserts a Flickr feed, or forums software installed fully-featured. Most other CMSs are often run on default installs, maybe with a module or two. That's a notable difference

1513:

In theory you're getting flexibility, that's what Drupal's scope is about, while most CMS' focus on one thing (forums, blogging, office documentation or even Wikis), Drupal tries to be able to all of those and whatever else too. Performance and Ease-of-Use are the trade-offs, both logically and in

790:

If you have evidence that Drupal's upgrade path is not seamless, please post it. That would be fair criticism, (e.g. "some users/reviewers/etc. have reported difficulty in upgrading their sites across major versions, such as from 5.13 to 6.0") But the article (as it was when I edited it) read as

773:

Anyone coming to the page is going to be looking for how the software operates, not how it could theoretically operate in the future. I don't think anyone could honestly say that Drupal's upgrade paths are currently seamless, most of the core developers would openly admit that it's not, that's why

683:

Next, the first sentence of this section reads: "Drupal's primary optimization is through caching oriented toward anonymous visitors which are not logged into the system. Performance tests with optimizations may not reflect actual usage in dynamic environments with logged in users and interactive

264:

I noticed you changed the picture size on this article back to a forced size of 300px. I've reverted that change, as well as replacing the br-clear code so the references fall properly on the page regardless of monitor width and resolution. Please leave this change in place to conform to the MoS

2740:

See notability comments above. And at the risk of repeating myself, Drupal's differences in structure and design should be a part of the article itself and to a degree they already are, whether they're a flaw is the point of stating the criticism in the first place. The reader can decide, we just

1244:

Drupal's modular structure, even within core, results in a large number of SQL and internal server requests which cause moderate-to-high usage performance-wise and serious concerns for scaling. The more modules added, the more the problem exasperates. The usual response is to use Drupal's default

886:

You want credit for not having the best wording and that's fine, that's exactly how Knowledge (XXG) grows, but you have not extended that courtesy to myself or others. Full on deletions of entire sub-sections however are something usually discussed on talk pages, etc. before you just go ahead and

1651:

Drupal is designed modular for flexibility. Easy to reference, but unnecessary. Each module makes its own SQL calls, so if the core is making many SQL calls compared to other CMS' it's logical and obvious to conclude that more modules with more SQL requests will be a greater total. 1 + 1 = 2. No

2666:

This whole thing could be wrapped into the nature / design of Drupal with pros and cons without even a criticism section, but I don't think I'm up to tackling the whole scope of the article. I guess I'm coming to the conclusion that without the overall article defining just what Drupal is, any

2505:

Digressing into personal opinion here: This is, in part, a frustration with Knowledge (XXG) as a sort of pop-culture encylopedia. A magazine and an award as examples of authoritative referencing, that does seem typical of reference requests. Using another example: A world-wide event happens and

2357:

Well I think that Drupal can be both a CMS *AND* a CMS framework. It is a bunch of parts that can be used to build a sophisticated web site, but is packaged by default in such a sample "basic" site. A (poor) analogy might be a box of legos-- you can buy a box of legos that are used to build a

2151:

It's notable that Drupal uses modules to achieve the same results of CMS' which are designed more as complete solutions. It's a different approach and in many ways defines Drupal. This is IMHO how the entire article should be oriented, on these sort of differences, because as it is, it's pretty

1983:

I am looking for any citation that performance/scalability is a notable issue in Drupal. A critical review, an online poll, a preponderance of "WHY IS DRUPAL SO SLOW?" posts from a wide-ranging number of users-- something! Right now you have a theory about more modules leading to more queries

1454:

Are you comparing to other CMS' or Frameworks? Frameworks, probably yes, CMS' typically no. There's modular and there's modular. Modularizing code (IE: code libraries) isn't the same as loading / unloading specific packages the way Drupal does. For instance the focus on modularity in code might

1273:

The next response is cache selectively at the SQL and server /code levels, but that's outside of scaling, or rather that's the usual response to scaling and not really a Drupal solution to the problem: It's part of the infrastructure system. This solution still performs best in less-interactive

1293:

Upcoming Drupal 7 attempts to fix the SQL requests problem (that in itself is arguably all the reference needed). I haven't looked at it too technically but my understanding is that they're attempting to merge SQL requests together as a sort of patchy fix. That's a tradeoff in code performance

1283:

So caching aside, Drupal scales poorly by default but great results can still be gained with infrastructure. That's a cure-all solution, just scale big enough until it's fixed. Worded at its most positive, you could suppose that support infrastructure is typically good enough now that Drupal's

844:

I don't know what edit you're talking about here. Again, I have no problem with an article criticizing Drupal's scalibility or performance (although my understanding is that Drupal is notably scalable). My problem was that the scalability section was half-baked- it was confusing, misleading,

829:

I don't think you agreed at all, you're going on now some more about alternative rhetoric on something that shouldn't be said in the article. If you are talking about forward-plans for Drupal, at the very least (note I did, but you deleted it) include a reference to the versions when that will

2396:

I've used the lego analogy too. Personally I'd say it's a Framework for creating a CMS (and delivery of content, but that's included in most CMS'). This is inherent in most of the practical usage: web design companies install, setup and customize / code Drupal sites for customers and then the

2212:

Exactly my thought. One could go to the forum and find examples of all kinds of issues people are having setting up Drupal. The other guy who posted his particular problem, something he hated about Drupal's default filtering behavior, simply disagreed with Drupal's design and posted it as a

1005:

There was one other editor who had a clear bias. If you'll fully read the history, you will see that a neutral third party agreed that my edits were appropriate. So I say to you, if you had some personal difficulty with Drupal, Knowledge (XXG) is not a place to vent your frustration, nor to

924:

I have no issues with you making changes, small undos, etc. but when you completely obliterate honest criticisms in a criticism section, you must understand that comes across extremely biased. It's as if you're defending Drupal and treating me as if I'm attacking it for referencing well known

1358:

I don't know if this begins to capture what you're talking about, but if so, I would hope that every statement above would be supported by citing sources, and that the issue itself would be demonstrated to be notable, ie "This problem has been cited as a reason for not adopting Drupal by XYZ

1340:, each unique module and theme may require their own database queries. Thus Drupal must consume more CPU cycles to create every page. This creates a problem for both Drupal's performance and scalability, as CMSs that do not support plug-in modules are better able to internally optimize 864:

Drupal strives to provide a seamless upgrade path" may have not been the best words to use. Although I do think that they are accurate.. "Drupal's policy is to provide a seamless upgrade path" may have been better. I'm fine with criticism, but it has to be real criticism, it has to be

3737:

is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

1455:

encapsulate SQL functions, whereas Drupal's modularity involves separating into building blocks for features. The closest comparative system is Joomla! / Mambo (Joomla! being a Mambo fork), so considering their comparison, Drupal's modularity is way out there from the rest of the crowd.

3833:

is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

1391:

That's a fair bit closer and more coherent. It's not so much that other CMS' don't also use modules, but that Drupal absolutely relies on them, right down to the core being made up of numerous modules. So out of the box defaults it's more taxing than other CMSs because it's already

1166:

In other words, if you're really so big on NPOV then walk the walk and prove it. Edit gracefully for a change. Personally I think you're probably just going to keep on using NPOV excuses to push your own mandated bias of software that you most likely have some financial dependence

3531:

and picked it up where I left off... Incidentally I think the intent of the three reversions is plainly to avoid a situation where people go back and forth endlessly reverting each other (via the revert button or by an effectively identical manual edit), but hey.. I'll leave the

2294:

Is the cache factor a well-known dispute? I'd never heard of it before you brought it up. So I'm inclined to say "no." Where have you seen this as a hot area of discussion? Please cite those sources, because I may be just out of it, but I haven't seen any talk about this...

752:

I completely disagree that Drupal's policy is useless information. The section read as though Drupal/Dries's policy was to casually break upgrade paths for the end user. That is not the case, so I added clarification to make it understood that this is not Drupal's practice.

1062:

The truth is, I use Drupal myself but not professionally. I'm not arguing on behalf of Joomla (have never used it) or any other CMS. These are well known and common criticisms from the Drupal community and I noticed a distinct lack of neutrally addressing them on the

1039:

The essence of bias? Give me a break. I am in favor of balance- I am in favor of fair criticism of Joomla, Drupal, whatever. And I am in favor of well-reasoned, written, and supported articles. If you make your section coherent and well-cited, I'm all in favor!

959:

If you have any interest in straightforward and balanced information on Knowledge (XXG), you would expand upon what I'd written rather than nuking it. I don't believe you really have an issue with NPOV at all, I think you have an issue with any criticism with Drupal,

2978:

With that said, I'm totally fine with drastically altering/merging/destroying that section (as one of your commit messages hinted at (I think)), I just hope we can keep enough reference links so that notability can be quickly established when the AfD wakes up again.

2543:

logic extends to first-person & original reporting. Knowledge (XXG) isn't a newspaper or a blog- it's meant to be an encyclopedic reference and include consensus information... but your point is very well taken, and I am sort of in the middle on the issue... --

3492:, "An edit or a series of consecutive edits that undoes other editors' actions—whether in whole or in part—counts as a revert." In the example I pointed to, you undid the action that inserted the word "widely". But you're right that the definition of "revert" at 3284:

Hi. I realise I focused almost entirely on the version history table back in November, but I meant for my comments to apply to the supported devices table as well. (I thought I mentioned that somewhere. Sorry if it was unclear.) The version history was really,

3473:

is. Removing an unneeded word at the end of a sentence is not a reversion of anything. It's a straightforward edit. It does not undo any specific prior edit and does not return the document to a previous state.... That's your example of a reversion? Huh?

3496:

is different. So I'll investigate some more and get back to you. One thing that I hope you see is that I was not (and am not) trying to accuse you of anything. I was merely offering a reminder, but you have pointed out a possible mistake on my part.

2251:

Isn't performance, though disputed (the cache factor), well enough known and impact related to be notable? The disputes themselves are an acknowledgment that it's a major issue. The criticism shouldn't need to prove one side or the other, just state it.

3664:

is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.

2473:

Personally, I can't speak to Drupal's adeptness at scaling. I get very few visitors to my site and haven't ever had to address it. Nevertheless, even if I had a horrible time scaling Drupal, it would be totally irrelevant to the article itself, as

791:

though it was Drupal's POLICY to allow such breakage. That is not the case. It is only the case from a developer standpoint (although one could argue that backward compatibility is desired, though often not possible), so that is what I clarified.

680:

real-world improvement due to non-anonymous users having customized content (and thus not using the cache), the cited article is overwhelmingly a favorable evaluation of Drupal's cache system. So why is it in a criticism section? Did YOU read it?

2899:

prohibits making more than three reversions on a single page within a 24 hour period. Additionally, users who perform a large number of reversions in content disputes may be blocked for edit warring, even if they do not technically violate the

1308:

I don't have a great urge to do this if I'm also fighting upstream. I'd like to see it in there, but if after reading what I've stated here you're not convinced it's valid for the article, then I'm not going to toss back and forth about it.

2397:

customer uses the end product as a CMS. I'd estimate that's most of Drupal's typical usage, which is much different than say Wordpress which is typically used by the end-user directly just as a blog CMS. That's a very notable difference!

2028:

Here's a thought-- maybe what you have is not actually a criticism of performance and scalability but a criticism of Drupal's modular design. In that case, the section should be called "Modular design" and might read something like

3292:

so that was the bigger problem. Although I do agree with Sudoghost about the supported devices I'm less bothered about it now that the version history is better, and tbh I'm not going fight over it. Hope that clears things up. –

1143:

I will take a look and make any edits I feel are appropriate. Sorry to step on your toes, but you're plain wrong about my "vested interest". The fact that you're making such assumptions should make you question your own POV.

1546:

same functionality as Drupal with all modules turned out may be faster as it could optimize databse calls, etc. But once you start turning off drupal modules you don't use, at some point drupal must gain the advantage. --

1836:, the new Civic may get another few MPG out of the engine, but that doesn't necessarily mean it would be appropriate to put a "criticism: mileage" section in the older civic's wikipedia article. See what I'm saying? -- 865:

understandable to the lay reader and it has to be accurate. The article left the impression that every time Drupal is upgraded it breaks the system for the end user-- it did not clarify this to be a (fair) criticism for

4181: 4093: 3939: 3861: 3765: 3692: 1237:

I'm getting tangled on wording the criticism plainly and non-technical while trying to come across as neutral as possible. I'll just explain more fully here so at least you know what I'm trying to have it explain:

3607:. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose 1332:

Due to its delivery of dynamic content and its "pluggable" modular design, Drupal operation tends to require more computational overhead than other CMSs that offer similar features. As Drupal custom-builds

3064: 1028:

I was interested in adding some balance for anyone using the Knowledge (XXG) entry to make an informed decision about software. I don't think you'll ever see it that way, which is the essence of bias.

4165:. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose 4077:. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose 3923:. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose 3845:. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose 3749:. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose 3676:. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose 3435:

policy. I haven't examined your edits closely enough to see if you've exceeded the 3RR threshold, but I figured it couldn't hurt to remind you about it, given the number of edits today. Cheers.

2358:

rocket ship-- the same legos can be used to build a train or a boat. There's a rocket on the box-- so you could say "This box contains a rocket, but it can also used to build other things..." --

3052:. We appreciate your contributions, but the nominator doesn't believe that the article satisfies Knowledge (XXG)'s criteria for inclusion and has explained why in his/her nomination (see also 1878:

I could find more articles noting many SQL queries and the pros and cons of modular design, but aside from getting outside of scope, it's just getting silly, how many references does it need?

1726:

A comparative benchmark is already referenced by that Dries article, it's just arguing that caching compensates the difference, but it documents that there's a difference in the first place.

4151: 4063: 3909: 1132:

let someone else clean it up (if anyone feels it's needed) or to at least leave the core criticism intact and edit without a defender's approach to put the software in absolute best light.

1006:

universalize your experience as typical. In other words, if the criticism is not notable and supported by something other than "original research", it should not be in the article. --

2976:- throw in a bunch of reference links that mention CyanogenMod (they all do, even when a title doesn't call it out) to help establish notability, since the AfD has merely been delayed. 3063:

Your opinions on whether the article meets inclusion criteria and what should be done with the article are welcome; please participate in the discussion(s) by adding your comments to

384: 2036:, both at the application and database levels can help mitigate this. Drupal's developers is working to address these concerns and improve performance via optimizations in Drupal 7. 1234:

Okay, taking a deep breath then because it sounds like we've rubbed each other the wrong way and both made assumptions. Not to mention similar backgrounds with the subject at hand.

1074:

If they are well-known and common then please explain in a clear fashion for non techhies, and includes support and I'll be the first one to slap you on the back and say thanks. --

925:

criticisms even within the core community of developers. This makes me assume you have a vested interest and if you do, you certainly shouldn't be anywhere near the article at all.

2741:

provide the information. It could be a lot more clear if there was less emphasis on trying so hard to prove / disprove it in a convoluted way rather than just using common sense.

1284:

relative performance is a non-issue. But in the end, what that does is limit Drupal to those whom have the infrastructure to support it, which does narrow Drupal's target market.

105:

instead of Knowledge (XXG). This makes them available to other language Wikipedias without the need for re-uploading. I've already uploading some of your images to Commons (see

639: 544:

After spending some time looking through all the edits, I think most of what Novasource is adding has a strong POV, and the sources that are referenced are not what I consider

371:

Welcome to Knowledge (XXG). Although everyone is welcome to make constructive contributions to Knowledge (XXG), at least one of your recent edits, such as the one you made to

2478:

are not sufficient for citation. If, on the other hand, Drupal had won CMS Magazine's "Least Scalable Web System" award for 2009, that might be a notable criticism.

3383: 1301:

most are logical conclusions based on the initial problem). It's based upon what I'd say is relatively common knowledge (except for the last bit with Drupal 7).

228: 3149: 1984:

leading to reduced real-world performance when caching is not turned on, or for those users who do not load cached content. I don't think this is enough. --

3322: 3159: 2189:

working solutions. Finding examples of non-working attempts or people bumping into the problems is easy, finding authoritative writeups / postmortems isn't.

3103: 3009:

until it satisfies Knowledge (XXG) requirements. Please help improving it and getting the necessary sources. We can move the article back once it's ready.

3145: 1832:

Again, there are probably many changes in Drupal 7. But an improvement in 7 doesn't necessarily correspond to a notable problem in 6. Going back to the

3378: 187:

I would like to ask you if it would be agreeable with you if I uploaded a newer version of the image referred to in the title of this discussion. Using

2847:

Please consider improving the article to address the issues raised because, even though removing the deletion notice will prevent deletion through the

2852: 2538:

but I do understand the argument. This may be a situation in which there is no perfect solution. It would be pretty crazy to have a policy which

1209:

If so, we have nothing to talk about, there's no point in trying to discuss something rationally with someone trying to protect their own arse.

744:-- Oh and specifically, "striving" to do something, or policy about something, in reference to software is absolutely useless information-wise. 3318: 3155: 82: 4204: 4115: 3961: 3875: 3779: 3706: 3632: 2821: 2628:

If you have that article about the cartoonistit would be great to show that this is a real-world (and not simply theoretical) issue. ---

2817: 3027: 2856: 1363:

be a problem but it's not really..." in which case it certainly doesn't belong. Anyway, that's my thought. I need to go eat now. --

2980: 3241: 1514:

reality. It's not unlike the old Jack of All Trades adage, if you focus on one thing then reusability of the parts isn't necessary.

309:

Then you haven't been reading the talk page very carefully. I have spent far more time explaining my edits than making them. --

26: 48: 4200: 4111: 3957: 3871: 3775: 3702: 3628: 994:

Now I'm looking back at the history and seeing that others have also had similar problems with your near-vandalistic deletions.

4174: 4086: 3932: 3854: 3758: 3685: 3253: 3209: 3152:). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. 2917: 43: 3315:. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. 2892: 1352:

by the database server itself, and proposed improvements for Drupal 7, may help mitigate such performance and scaling issues.

725:

Does it mean anything that Drupal is faster than Joomla with caching turned on? What is the relationship to scalability? --

593:

Please note i'm hardly an admin... and while I still stand by what I said, please try to keep a civil attitude! best wishes,

549: 387:

to learn more about contributing to this encyclopedia. Your edits continue to be nonconstructive and have risen to vandalism.

142: 3553:

The rules could be a lot clearer, and the results depend a lot on which adminustrator gets involved. Anyway, happy editing.

3257: 2901: 2896: 2799: 405:

For the record, Novasource is harassing me because he doesn't like edits I made regarding his lack of NPOV and use of OR. --

902:. If you want to fix the section, put it back. I looked at it and couldn't even figure out what it was trying to say. -- 500:, and particularly his edits]. Novasource, your repeated unfounded warnings, edit-warring, false claims of vandalism, and 292:. Your contributions are increasingly nonconstructive and nonsensical for reasons I have outlined in the Drupal talk page. 1274:

environments. The more that's unique, the less can be cached, right? The benchmarks are far removed from real-world usage.

3045: 266: 2431:

XYZ survey showed that 56% of drupal sites are used for corporate, 14% political, 20% personal, and 10% "other" purposes

2081:

dispute that Drupal is focused like most other CMS', what is disputed is whether Drupal is better in its modular design.

3619:

describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to

3263: 2907: 2825: 481: 453: 53: 4186: 4098: 3944: 3866: 3770: 3697: 3624: 1294:

because they aren't merged to start, they come out in branches and are recombined, so slowing down in PHP makes sense.

3205: 1305:

to drive a stake somewhere with it, it just made sense to me as the first stop where people will look for the info.

662:

the article (from Dries Buyart no less) didn't apply. If you dislike the wording, reword it in an unbiased fashion.

168:

Way to be bold in tossing out the actor's section of the WGA page. It was time for something to be done, great job!

3796: 3488:

That's an interesting reply, thanks. It may also be that neither of us knows what a revert is. :-) According to

3307:

Hi. Thank you for your recent edits. Knowledge (XXG) appreciates your help. We noticed though that when you edited

3558: 3521: 3502: 3460: 3440: 2841: 258: 3249: 3221: 3197: 2912:. Please do not repeatedly revert edits, but use the talk page to work towards wording and content that gains a 240: 33: 22: 4031: 4014: 3990: 647: 223: 188: 4162: 4074: 3920: 3842: 3746: 3673: 2806:, suggesting that it be deleted according to the proposed deletion process because of the following concern: 101:

Thanks for all the images of the WGA strikes. Since they are all PD you may want to look at uploading them to

60: 3006: 3002: 2995: 2803: 3053: 1585:

from Drupal, even just on the default install (and my experience with Drupal is default installs are rare).

810: 505: 64: 4027: 4010: 3986: 3413: 3620: 3245: 3213: 2913: 2860: 473: 449: 429: 76: 68: 2984: 2868: 200: 113: 3088:. I have nothing to do with this article or the deletion nomination, and can't do anything about it. -- 2888: 501: 38: 2974:- write in plain english the main benefit of that firmware (not my native tongue though, and it shows) 428:

Please refrain from making unconstructive edits to Knowledge (XXG). Your edits appeared to constitute

3804: 3554: 3517: 3498: 3456: 3436: 3133: 3093: 2952: 2940: 600: 564: 392: 299: 173: 4145: 4057: 3903: 3829: 3733: 3660: 3642: 3596: 3587: 437: 380: 232: 3271: 2864: 2833: 643: 4158: 4070: 3916: 3838: 3742: 3669: 3616: 3600: 2840:

notice, but please explain why you disagree with the proposed deletion in your edit summary or on

545: 3118: 149: 29:. I hope you like the place and decide to stay. Here are some pages that you might find helpful: 3216:

rather than repeatedly undoing other users' edits once it is known that there is a disagreement.

1652:

references needed, it's really just simple additive math, you can't get simpler logic than that.

610:

Sorry, thought green signified admin for some reason ;) But I'm glad to see others agree too --

1909:

It needs a reference that overall, Drupal's performance/scalability is a problem for people. --

1345:

of the benefit of caching. Other solutions, including caching only blocks, forms, and themes,

106: 75:(~~~~); this will automatically insert your username and the date. If you need help, check out 3409: 3358: 3338: 3175: 236: 235:

for testing; if you believe the edit was constructive, ensure that you provide an informative

4170: 4082: 3928: 3850: 3754: 3681: 3612: 3604: 2848: 899: 4193: 4105: 3951: 3312: 3074:

You may also edit the article during the discussion to improve it but should not remove the

2672: 2591: 2257: 2157: 1334: 1314: 1214: 835: 804: 779: 710: 667: 274: 248: 196: 109: 88: 4173:, editing restrictions, and other measures needed to maintain our editing environment. The 4166: 4085:, editing restrictions, and other measures needed to maintain our editing environment. The 4078: 3931:, editing restrictions, and other measures needed to maintain our editing environment. The 3924: 3853:, editing restrictions, and other measures needed to maintain our editing environment. The 3846: 3757:, editing restrictions, and other measures needed to maintain our editing environment. The 3750: 3684:, editing restrictions, and other measures needed to maintain our editing environment. The 3677: 3615:, editing restrictions, and other measures needed to maintain our editing environment. The 3608: 3489: 3432: 3365:

that an edit performed by you may have introduced errors in referencing. It is as follows:

3085: 3075: 3068: 3057: 3800: 3536: 3475: 3089: 3017: 2948: 2925: 2703: 2629: 2544: 2434: 2359: 2296: 2214: 2112: 2039: 1985: 1910: 1837: 1759: 1685: 1614: 1547: 1417: 1364: 1188: 1145: 1110: 1075: 1041: 1007: 973: 938: 903: 870: 846: 754: 726: 689: 611: 594: 579: 558: 509: 492: 406: 388: 349: 329: 310: 295: 169: 2475: 4023:

And i had a small edit in that page please say ur mind as my first edit in en wikipedia

3493: 3470: 3401: 3268: 2943:

page, that speedy delete irritated me, if nothing else the debate this has engendered (

2770:

I'm getting worn out on this, it's really fairly simple and being made overcomplicated.

1952:

over-policing and making it difficult to contribute. This is what annoyed me initially.

433: 376: 3044:

An editor has nominated one or more articles which you have created or worked on, for

2883: 2816:

All contributions are appreciated, but this article may not satisfy Knowledge (XXG)'s

444: 3428: 3370: 3329:

It's OK to remove this message. Also, to stop receiving these messages, follow these

3166:

It's OK to remove this message. Also, to stop receiving these messages, follow these

3114: 3078:

template from the top of the article; such removal will not end the deletion debate.

139:

You should watch your language, otherwise I'll inform authorities. (: - Yours truly,

87:

before the question on your talk page. Again, welcome! And thanks for the pictures!

2791: 1264:

The problem is further exasperated by modules that conflict with the caching system.

3334: 3330: 3171: 3167: 3110: 1613:

critique is based in fact and well-explained, we need to ask if it is notable... --

972:

the likely motivation. Are you sure you're not being paid to edit? Oh, I kid. --

937:

technical, and did not address the critique of overall performance/scalability. --

123: 4137: 4049: 3895: 3820: 3724: 3651: 3513: 2972:

I had primarily two purposes in starting the "User benefits"/"Philosophy" section:

3308: 3201: 3049: 3031: 2970:

page, it definitely needs help (another speedy delete survivor too, apparently.)

2967: 2668: 2587: 2253: 2153: 1833: 1310: 1210: 831: 800: 775: 706: 663: 497: 270: 244: 192: 3037: 460: 269:. This prevents the picture from overriding individual preference settings. -- 3400:

Please check this page and fix the errors highlighted. If you think this is a

3294: 3013: 2921: 1337: 348:

I'm cleaning up the page by merging Novasource's warnings to one section. --

2152:

confusing what exactly Drupal does if one goes by the Knowledge (XXG) entry.

3231:; that is to say, editors are not automatically "entitled" to three reverts. 3141: 288:

This is a notice that I will now be more free about reverting your edits to

3999: 3980: 108:). Adding them to articles on Knowledge (XXG) is exactly the same, (ie ]). 799:

The point is, the Drupal page should be informational, not advertisement.

122:

Seriously, thanks a lot for the images. Let me know if you need any help.

3244:

to discuss controversial changes; work towards a version that represents

1341: 4208: 4177:

describes the Committee's roles and responsibilities in greater detail.

4119: 4089:

describes the Committee's roles and responsibilities in greater detail.

4035: 4018: 4004:

This guy is deleted and had one warning cuz of his pro-antiregime edits

3994: 3965: 3935:

describes the Committee's roles and responsibilities in greater detail.

3879: 3857:

describes the Committee's roles and responsibilities in greater detail.

3808: 3783: 3761:

describes the Committee's roles and responsibilities in greater detail.

3710: 3688:

describes the Committee's roles and responsibilities in greater detail.

3636: 3562: 3544: 3525: 3506: 3483: 3464: 3444: 3417: 3342: 3297: 3274: 3179: 3122: 3097: 3021: 2988: 2956: 2929: 2872: 2711: 2676: 2637: 2595: 2552: 2442: 2367: 2304: 2261: 2222: 2161: 2120: 2047: 1993: 1918: 1845: 1767: 1693: 1622: 1555: 1425: 1372: 1318: 1218: 1196: 1153: 1118: 1083: 1049: 1015: 981: 946: 911: 878: 854: 839: 814: 783: 762: 734: 714: 697: 671: 651: 619: 605: 587: 517: 468:

you will receive for your disruptive edits, such as the one you made to

424: 414: 396: 367: 357: 318: 303: 278: 252: 214: 204: 177: 158: 128: 116: 91: 4155:

are allowed to vote. Users with alternate accounts may only vote once.

4067:

are allowed to vote. Users with alternate accounts may only vote once.

4007:

I just want to please suggest a way to pervent of these kind of issues

3913:

are allowed to vote. Users with alternate accounts may only vote once.

3603:

is the panel of editors responsible for conducting the Knowledge (XXG)

3229:

Edit warring is disruptive regardless of how many reverts you have made

2033: 1349: 3532: 469: 372: 289: 2947:) is helpful, and will probably justify it's notability over time. 1230:

An Explanation on the Drupal Criticism of Performance / Scalability

3065:

Knowledge (XXG):Articles for deletion/CyanogenMod (3rd nomination)

2944: 383:

for any test edits you would like to make, and take a look at the

72: 4190:. If you no longer wish to receive these messages, you may add 4102:. If you no longer wish to receive these messages, you may add 3948:. If you no longer wish to receive these messages, you may add 4180:

If you wish to participate in the 2021 election, please review

4092:

If you wish to participate in the 2020 election, please review

3938:

If you wish to participate in the 2019 election, please review

3860:

If you wish to participate in the 2018 election, please review

3764:

If you wish to participate in the 2017 election, please review

3691:

If you wish to participate in the 2016 election, please review

2111:

WP article is noting a criticism of Drupal's modular design. --

231:

has been reverted, as it appears to be unconstructive. Use the

4149:

is now open until 23:59 (UTC) on Monday, 6 December 2021. All

4061:

is now open until 23:59 (UTC) on Monday, 7 December 2020. All

3240:

If you find yourself in an editing dispute, use the article's

3137: 1346: 79:, ask me on my talk page, or ask your question and then place 3188: 3036: 2851:, the article may still be deleted if it matches any of the 2790: 887:

nuke a large chunk of something someone else was working on.

213: 3256:. In some cases it may be appropriate to request temporary 2828:). You may prevent the proposed deletion by removing the 1109:

Just write a good section and support your assertion! --

3907:

is now open until 23:59 on Monday, 2 December 2019. All

2820:, and the deletion notice should explain why (see also " 191:, I brightened the shadows seen in the image (mostly on 4161: