Thanks for the replies!
> For the future, Andy's suggestion of a "hook" in HTTP execution for
> manipulating requests sounds like a good one. Would that meet your needs,
> and if so, will you please file a ticket for it?
Yes, that would be great! Y’all already have a hook for responses so one
>
>
> Hello,
>
> I have been generated rdf/xml file from Pretege.
> I am trying to load it in android studio by using the following code:
>
> Model m =
> FileManager.get().loadModel("C:\\Users\\Toshiba\\AndroidStudioProjects\\MyApplication\\app\\sampledata\\MallOntology.owl")
> ;
>
> but I
On 14/09/18 14:18, Markus Neumann wrote:
Hi Andy,
thanks for pointing that out.
what would you recommend as a heap size?
From a pure storage point of view, 2-4G per dataset.
Query can take some workspace, and HTTP handling, as can other Jena modules.
And Java itself.
And the minimum
Note that you can use "pigz" to parallelize your gzip compression. It
scales roughly linearly with the number of CPU cores.
Similarly "pbzip2" for bzip2.
Unimportant here, but note that pbzip2 also decompresses in parallel if
it did the compression. Normal bzip2 can still uncompress.
Andy
Hi Andy,
thanks for pointing that out.
what would you recommend as a heap size?
> Am 14.09.2018 um 15:04 schrieb Andy Seaborne :
>
>
>
> On 12/09/18 16:08, Markus Neumann wrote:
>> Hi,
>> we are running a Fuseki server that will hold about 2.2 * 10^9 triples of
>> meteorological data
> On Sep 14, 2018, at 8:57 AM, Andy Seaborne wrote:
> On 10/09/18 16:08, Niraj Patel wrote:
>> Thank you both for replying!
>>> Can you tell us more about your use case? Are the custom headers for some
>>> one particular purpose?
>> Sure! So our database, Allegrograph, allows us to pass down
On 12/09/18 16:08, Markus Neumann wrote:
Hi,
we are running a Fuseki server that will hold about 2.2 * 10^9 triples of
meteorological data eventually.
I currently run it with "-Xmx80GB" on a 128GB Server. The database is TDB2 on a
900GB SSD.
Not sure if this is mentioned later in the
On 10/09/18 16:08, Niraj Patel wrote:
Thank you both for replying!
Can you tell us more about your use case? Are the custom headers for some one
particular purpose?
Sure! So our database, Allegrograph, allows us to pass down custom headers
while querying or updating in order to store
I will do. Thanks a lot for all your help already.
If anyone else would happen to run into this, here is how I'm handling the
updates now:
I have a base_db, created with tdbloader2, containing the steady part of our
dataset.
The Fuseki server config always reads the database from prod_db.
As
I remember giving or reading advise on this here on the mailing list. if
you can't find it here please consult the old jena archive mailing list.
if you still can't find the answer to this question please open a new
thread and we will take it from there.
On Fri, Sep 14, 2018 at 6:36 AM Markus
10 matches
Mail list logo
