Open cfrancois7 opened 7 years ago
I found something. When I use elinks or w3m (two cli browers) everything is very reactive. I can't explain why ?
It is a mean to load only the data necessary in the page of requested Ontowiki and not the entire database?
I'm thinking the problem comes from the navigation module. The "is large" option of the knowledge base is activated. And when I disable the navigation module, everything works fine, but I haven't any more the navigation. It takes a lot of time to load classes and during this time it is impossible to use ontowiki properly.
I don't know why It takes so much time to load the classes even on the original knowledge base.
The navigation spends approximately 5 minutes to stop searching.
The menu spends a similar time.
The problem is the way the navigator module behaves with my data and my ontology. I looked the helps (here) but I didn't success to get a good navigation. It is not the data but the ontology which is quite heavy. What kind of config do you recommend?
Hello,
I'm currently using the ontowiki platform with a virtuoso backend about 21 Go of data on a MacOsX:8 Go 1600 MHz DDR3, 2,4 GHz Intel Core i5.
My config is Nginx - php-ftp - virtuoso on localhost. Everything seems fine with the virtuoso machine, but ontowiki is almost impossible to use because it is too slow.
[error] 17399#0: *397 upstream timed out (60: Operation timed out) while reading response header from upstream, client: ::1, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "localhost"
The problem occurs also when I want to clear the cache. I found no solution in the log. But more the database was, more longer ontowiki replied. Even to clear module cache.
php-fpm.txt php.ini.txt php-fpm.conf.txt ontowiki.conf.txt nginx.conf.txt config.ini.txt virtuoso.ini.txt