Search Results

Yes, large variable tables are a problem. Variables should only be used for small configuration flags and settings and not to store large structures for example. But given a large amount of modules, …

There is no other way that I know of in Drupal 6. Drupal 7 has node_load_multiple(), which allows to load multiple nodes in a single query (+ hooks, which can also do single queries for multiple node …

No chance, hiding doesn't help, drupal will still load all values even if the field is hidden. You could add the reference field on the item type and then load them through a view. Or use the rela …

It sounds like you're affected by a known issue in Drupal 7. Most probably, you are hitting Avoid re-scanning module directory when multiple modules are missing. It happens if you have some missin …

The advantage of field API is that the storage is pluggable, so you could for example use it together with MongoDB which could possibly drastically improve the performance, with some drawbacks however. …

After looking at the numbers above, I imagine that the performance gains of doing this in Drupal 7 would be quite a bit smaller. … That one pretty much undoes all the performance work that went into Drupal 7. Let's see how it looks in Drupal 8, if Twig makes it into core. Lastly, about the mentioned advantages. …

MongoDB is not a full replacement for MySQL, you still need it. You can only move certain pluggable systems to MongoDB, like sessions, watchdog and in Drupal 7 also the field storage.

Having multiple webservers behind a load balancer/reverse proxy is quite common for Drupal and well supported. Varnish is typically used in the Linux world because that thing is just insanely fast whe …

However, D8 has a number of things that are hopefully going to make more than up for that on real sites Javascript by default runs in the footer, which improves front-end performance, as pages build … Also keep in mind, if you care about performance, then you're very likely not running vanilla D7/D8 sites, you have large sites with a lot of content. …

Pretty sure that report is bogus. That's just an arbitrary method, not a controller. They somehow identify that as the controller for that request but of course that doesn't make sense. That page li …

But also here, the argument is most likely not going to be runtime performance, parsing code is really, really fast. … It's your performance in understand the code, finding bugs, writing test and so on. Optimize for that. …

A lot of the bootstrap process happens now implicitly as services are requested. If nothing requests the database service then Drupal won't open the connection to it and so on. The minimal amount of …

The amount of data in a field usually isn't a problem. If you're worried about that, look into alternative field storage plugins or write your own. For example MongoDB, which can deal with pretty much …

load() and loadMultiple() are cached, loadByProperties() is a shortcut for an entity query + load, the entity query is not cached. Do not use loadByProperties() if you know the entity ID.

A bit late, but especially if you are using that ajax callback for polling (check for new messages for example), there is an interesting alternative: Drupal node.js integration. Instead of polling, i …