Hi, Steven,
The particular block of code is attempt to restablish .sp file. When
the data file is missing is simply writing a bunch of 0s. I see that
it is not particularly helpful, especially when the user has
explicitly removed the data file. Will remove this code block in the
next release.
John
On 10/13/15 7:49 PM, Enns, Steven wrote:
> Hi John,
>
> Under high load we observe unusually high kernel CPU, many write
> syscalls originating from text::startPositions, category.cpp:1547. We
> have removed the raw data files from our text indexes to conserve disk
> space and queries seemed to function without them. Can you help me
> understand what is the purpose of this write call? Do we need to keep
> the raw data files?
>
> const bool isActiveData = (thePart->getStateNoLocking() ==
> ibis::part::STABLE_STATE && (dir == thePart->currentDataDir() ||
> std::strcmp(dir, thePart->currentDataDir()) == 0)); if (fdata == 0) {
> // failed to open data file, assume it is empty if ((isActiveData ||
> thePart->currentDataDir()== 0) && thePart->nRows() > 0) { rewind(fsp);
> nold = thePart->nRows(); for (unsigned j = 0; j <= nold; ++ j) (void)
> fwrite(&pos, sizeof(int64_t), 1, fsp); } fclose(fsp); return; }
>
>
>
>
>
>
>
> _______________________________________________
> FastBit-users mailing list
> [email protected]
> https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
>
_______________________________________________
FastBit-users mailing list
[email protected]
https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
