[SMW-devel] [News] Wikidata launching soon; press release

2012-03-30 Thread Markus Krötzsch
Dear SMW users & developers,

many of you are already aware of the Wikidata project [1] -- a major 
effort to establish a platform for editing and sharing data among all 
Wikipedia communities. The project will start next Monday, 2 April 2012. 
A few moments ago, the official press release on Wikidata has been 
issued by Wikimedia Germany e.V.:

DATA REVOLUTION FOR WIKIPEDIA
Wikidata will be the first new Wikimedia project since 2006
http://www.wikimedia.de/wiki/Pressemitteilungen/PM_3_12_Wikidata_EN

The technical work will largely be documented online, and there is also 
a mailing list wikidata-l [2] for announcements and discussions that you 
might find interesting.

Exciting times.

Cheers,

Markus

[1] http://meta.wikimedia.org/wiki/Wikidata
[2] https://lists.wikimedia.org/mailman/listinfo/wikidata-l

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] Using a cron Job to save Semantic Properties

2012-03-30 Thread Jeroen De Dauw
Hey,

> Both Memcache and APC can run in parallel so we might also consider using
both

Installing APC gives you a performance boost, even if the app does not
really do effort to take care of the cache.

I'm for a cache-type agnostic approach, ie one where you just cache things
wherever they should be cached according to the wikis config and available
caching tools. I recommend you have a look at wfGetCache in MediaWikis
GlobalFunctions.php, and the related functions that can be found near it.
Unfortunately there do not appear to be any docs on this. I've been using
wfGetCache( CACHE_ANYTHING ) a lot recently, which can work with memc when
available, but is also very effective when it's not (when stuff is stored
in the db).

The main questions for this project are probably not how to cache stuff (as
MediaWiki already provides the facilities you need), but rather what to
cache, when to cache it, and how to properly invalidate it (if needed).

An easy place to start would be SMWs special pages such as
Special:Properties, Special:Types and Special:SemanticStatistics (or
something like that). There you can easily cache the HTML output, and then
when the page is hit again, and is still in the cache, just use the build
up HTML, sparing you the need to do any queries (except the single one
obtaining the HTML) and the cost of rendering the page itself.

I wrote some generic utilities to cache special pages (for some other
extension), which we might want to use here, although I think it'd be best
if you just did a page without first, so you know how the stuff works, and
can use it where those utilities are not helpful :)

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] Using a cron Job to save Semantic Properties

2012-03-30 Thread Niklas Laxström
On 30 March 2012 17:36, Jeroen De Dauw  wrote:

>> Both Memcache and APC can run in parallel so we might also consider using
>> both
>
> Installing APC gives you a performance boost, even if the app does not
> really do effort to take care of the cache.

Agreed. Installing APC is something that we as developers cannot do on
users behalf.

> The main questions for this project are probably not how to cache stuff (as
> MediaWiki already provides the facilities you need), but rather what to
> cache, when to cache it, and how to properly invalidate it (if needed).

Especially the invalidation is tricky.

> An easy place to start would be SMWs special pages such as
> Special:Properties, Special:Types and Special:SemanticStatistics (or
> something like that). There you can easily cache the HTML output, and then
> when the page is hit again, and is still in the cache, just use the build up
> HTML, sparing you the need to do any queries (except the single one
> obtaining the HTML) and the cost of rendering the page itself.

Don't forget i18n. On particular complex pages you might need to cache
both the queried and processed data and the generated html output for
each language.

In special I'm most concerned of the buildup of queries on normal page
views, that happen much more often that special page views and they
add up to lot to decrease general snappiness.

  -Niklas

-- 
Niklas Laxström

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] Using a cron Job to save Semantic Properties

2012-03-30 Thread Jeroen De Dauw
Hey,

> In special I'm most concerned of the buildup of queries on normal page
views,
> that happen much more often that special page views and they add up to
lot to decrease general snappiness.

Yeah, definitely, I actually said this in one of my earlier mails, and did
not mean to push SMWs special pages as high priority. I simply think they
are a good place to start (if you still need to learn this stuff), since
caching them is relatively straight forward.

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


Re: [SMW-devel] Using a cron Job to save Semantic Properties

2012-03-30 Thread nischay nahata
On Fri, Mar 30, 2012 at 10:24 PM, Jeroen De Dauw wrote:


> Yeah, definitely, I actually said this in one of my earlier mails, and did
> not mean to push SMWs special pages as high priority. I simply think they
> are a good place to start (if you still need to learn this stuff), since
> caching them is relatively straight forward.


Yes, Its better to start with something easy. I have already started to
work on caching Special Pages.

-- 
With Regards

Nischay Nahata
B.tech 3rd year
Department of Information Technology
NITK,Surathkal
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel