By bilgehan on

Hi,

I'm planning to construct an encyclopedia/dictionary like system. More like wikipedia. The reason I want to use drupal instead is its flexibility and its features like blogs etc.

What I want to make is a bilingual knowledgebase: Spanish-Turkish.

First I need to import about 50.000 spanish words and another 50.000 turkish words with their definitions, Then I'll let people to edit the contents in a colaborative way. I want to have the path alising module for all nodes

There will be also articals, blogs and image galleries.

I don't expect a lot of traffic at the beginning but I worry about the performance of the site for working with such a large database?

So is this possible with drupal?

Thanks a lot in advance for your help and comments.

⋅ Categories: Drupal 4.7.x

Comments

dries’s picture

dries commented

MySQL can handle it. PHP can handle it. Drupal can handle it. Whether your site will be responsive depends on (i) your hardware, (ii) the modules you plan to use and (iii) the number of concurrent users. In other words: we can't tell based on the information you provided.

green monkey’s picture

green monkey commented

I'm interested in your progress, could you please keep us informed on your project.

thanks

bilgehan’s picture

bilgehan commented

I still spend most of my time in learning Drupal, Php and Mysql. Until I get a site like this in life, I suppose I will be in the forums for a long time.

bilgehan’s picture

bilgehan commented

Thanks Dries. What a pleasure getting from you such a quick reply!

(i)Hardware

I will get whatever the site needs to. I was thinking to hire a hosting of 20-30 euros a month though. About this I have very little idea. I appreciate your comments. Do I have to buy a dedicated hosting or buy my own hardware?

(ii)The modules I plan to use

  • Core Modules
  • Contributed Modules:
    • Checkout
    • Diff
    • Event
    • Folksonomy
    • freelinking
    • Gallery
    • Image
    • Img_assist
    • Pathauto
    • SQL Search (Trip Search)
    • TinyMCE WYSIWYG Editor
    • Urlfilter

(iii)The number of concurrent users

I expext few users at the beginning like 20-30. In the near future the number can be 100.

pamphile’s picture

pamphile commented

From my experience pathauto really draws resources...

cel4145’s picture

cel4145 commented

I tried the mass alias option on Kairosnews which is about 4500 nodes. First of all, it had problems aliasing them all (no idea why). Second, it was noticeably slower, so I removed almost all of the aliases.

pamphile’s picture

pamphile commented

wow, like this will soon be a issue of the past.

see: http://drupal.org/node/38429

Marcel
http://www.macminiforums.com

cel4145’s picture

cel4145 commented

I use pathauto on a smaller site, and really like it. Once the performance issues is gone, I would think it makes sense to use it on almost any site (well, other than those where the admin wants to create the aliases).

sangamreddi’s picture

sangamreddi commented

Hi,

The pathauto is good but it creates the aliases in the tables. If a large site like this, it has to store more data.

I was thinking that soemone could create a dynamic path module. which creates the path dynamically, instead of storing paths in the database.

just found the link
http://www.greenash.net.au/posts/thoughts/hierarchical_url_aliasing

It's only my opinion.

Sunny
www.gleez.com

tclineks’s picture

tclineks commented

Do it!

Why not benchmark by inserting many 'Lorem Ipsum' nodes? And coresponding aliases.

This would be simple to script.

It'd be nice to have some figures.

morphir’s picture

morphir commented

What about using zend optimizer to see what is taking resources?

peterx’s picture

peterx commented

Drupal will probably handle more than you need before you need it.

Read http://drupal.org/node/35909 for an example where Drupal contained a bottleneck that hit only one large site out of many large sites using Drupal. The bottleneck was removed in seven days.

Your results will depend on the number of visitors that are active, the percentage that are logged on and the combination of options you use. If you have a combination that does produce a performance problem then supply the type of information mentioned in http://drupal.org/node/35909 and someone can help you.

The slower parts of Drupal are the parts that do the most work for the visitor and they are generally the parts that you supply to users when they are logged on. Users who register and log on are often providing content that attracts other visitors. Registered are worth a few extra dollars for extra memory and a faster processor.

petermoulding.com/web_architect

petermoulding.com/web_architect