I'll add that the LARQ plugin for Fuseki (which adds Lucene indexes) is pretty awesome, as well.
On Feb 20, 2013, at 3:57 PM, John Fereira <[log in to unmask]> wrote:
> If forgot about that. That issue was created quite awhile ago and I hadn't check on it in a long time. I've found that Jetty has worked fine in our production environment so far. As I wrote earlier, I have it connecting to a jena SDB that is used for a semantic web application (VIVO) that was developed here. Although we have the semantic web application running on a different server than the SDB database I found the performance was fairly significantly improved by having the Fuseki server running on the same machine as the SDB.
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Ethan Gruber
> Sent: Wednesday, February 20, 2013 2:52 PM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] Fuseki and other SPARQL servers
> Hi Hugh,
> I have investigated the possibility of deploying Fuseki as a war in Tomcat (
> https://issues.apache.org/jira/browse/JENA-201) because I wasn't sure how the default Jetty container would respond in production, but since you aren't having any problems with that deployment, I may go ahead and do that.
> On Wed, Feb 20, 2013 at 2:39 PM, Hugh Cayless <[log in to unmask]> wrote:
>> Hi Ethan!
>> We've been using Jena/Fuseki in papyri.info for about a year now, iirc.
>> We started with Mulgara, but switched. It's running in its own Jetty
>> container in our system, but I've had no performance issues with it
>> On Feb 20, 2013, at 14:31 , Ethan Gruber <[log in to unmask]> wrote:
>>> Hi all,
>>> I have been playing around with Fuseki (
>>> http://jena.apache.org/documentation/serving_data/index.html) for a
>>> few months to get my feet wet with accessing and querying RDF. I
>>> quite like it. I find it well documented and easy to set up. We
>>> will soon deploy a SPARQL server in a production environment, and I
>>> would like to know if others on the list have experience with Fuseki
>>> in production, or have
>>> recommendations. Mulgara is off the table as it inexplicably
>>> conflicts with other apps installed in Tomcat.