here:
https://phoenix.apache.org/tuning_guide.html and it's accessible through the
Using->Tuning menu time.
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/j
help, especially [~jamestaylor], [~apurtell],
[~elserj], and [~samarthjain].
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
>
get this pushed out to the website shortly.
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
>
and let me know what you think of my
additions to the sections you mentioned. They're both short additions.
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/
[
https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Conrad updated PHOENIX-3218:
--
Attachment: Phoenix-Tuning-Guide-20170324.md
Added info about column mapping and immutable
you if you can make those edits today.
Otherwise, [~samarthjain] or another committer can commit next week (I'm out
next week).
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issue
5 PM:
Thanks! [~apurtell], if you agree, can you commit for me?
[edit] After I make [~jamestaylor]'s suggested edit, of course.
was (Author: pconrad):
Thanks! [~apurtell], if you agree, can you commit for me?
> First draft of Phoenix
can you commit for me?
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
> Issue Type: Improvem
raft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Peter Conrad
nrad]!
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
> Issue Type: Improvement
>
section.
Perhaps both can have a pointer to the blog?
+1 after that. WDYT, [~elserj]?
[1] https://blogs.apache.org/phoenix/entry/column-mapping-and-immutable-data
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
>
t we can either do the next round of edits
or wrap this one up. Any comments [~apurtell], [~jamestaylor]? Anyone else?
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/
[
https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Conrad reassigned PHOENIX-3218:
-
Assignee: Peter Conrad
Flags: Patch
> First draft of Phoenix Tuning Gu
[
https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Conrad updated PHOENIX-3218:
--
Attachment: Phoenix-Tuning-Guide-20170223.md
Made edits in response to comments since
doesn't need to
buffer them).
Thanks for the details. I learned something new.
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
>
swer helps a lot. Any insight on the questions
about hardware recommendations or GZIP?
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
>
the
questions about hardware recommendations or GZIP?)
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
>
swer helps a lot. Any insight on the questions
about hardware recommendations or GZIP?
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
>
yet. If you have auto commit on, then
Phoenix is able to write the DELETEs directly on the region servers without
returning the rows back to the client (since it doesn't need to buffer them).
> First draft of Phoenix Tuning Guide
> ---
>
&
re reliable way to determine cache update
frequency?
I think 15mins is a fine value -- my suggestion was just to use stronger
language in stating it.
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
>
sh Elser says:
_Reasoning behind this one isn't clear to me. Batching DELETEs would have the
same benefit of batching UPSERTs, no? (I may just be missing an implementation
detail here..._
*Can you help me answer his questions?*
> First draft of Phoenix Tuning Guide
> --
tion
detail here..._
*Can you help me answer his questions?*
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: P
m
fine with it. What do people think?
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
> Issue T
etail here..)
The explain section is *fantastic*. Great job there. Overall, this is a very
nice write-up you've put together, [~pconrad]! I think a little bit of
tweaking, and this will be an often-reference document.
> First draft of Phoenix Tuning Guide
> ---
te, Peter.
>
> I'll try to give it a glance.
>
> Peter Conrad wrote:
>
>> The Phoenix Tuning Guide has been through several reviews and revisions.
>> The latest version is attached to PHOENIX-3218:
>>
>> https://issues.apache.org/jira/browse/PHOENIX-3218
>>
&
way through. don't want JIRA to eat my
comments while editing)
{code}
# Phoenix Tuning Guide
{code}
"Apache Phoenix" for the first reference in the doc, please.
{code}
*This guide was written by [Peter Conrad](https://github.com/pconrad-fb) in
September 2016 to help Phoenix user
Thanks for sending a note, Peter.
I'll try to give it a glance.
Peter Conrad wrote:
The Phoenix Tuning Guide has been through several reviews and revisions.
The latest version is attached to PHOENIX-3218:
https://issues.apache.org/jira/browse/PHOENIX-3218
Please take a look and comment
The Phoenix Tuning Guide has been through several reviews and revisions.
The latest version is attached to PHOENIX-3218:
https://issues.apache.org/jira/browse/PHOENIX-3218
Please take a look and comment with any final feedback.
Thanks,
Peter
Peter Conrad
Lead Technical Writer
[
https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Conrad updated PHOENIX-3218:
--
Attachment: Phoenix-Tuning-Guide-20170110.md
Made significant format edits, cleaned up a few
... still in progress but
putting this version up so you can see the changes.
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
>
ould it ideally be reduced from beginning itself given it is almost
same as region size?
We can also mention in the document that if we are reducing the size of the
guideposts, then phoenix.query.queueSize may need increasing as more work will
be queued thereafter.
> First draft of Phoenix
es a flat
keyspace with single key for lookup and does not imply a partitioning scheme.
In contrast, HBase (and BigTable) presents multiple keyspaces (aka tables) and
is a distributed ordered tree.
> First draft of Phoenix Tuning Guide
> ---
>
>
y to move all of the JVM and Operating-System
config tunings (e.g. Nagle's, THP, garbage collection) into the HBase book
I'd commit such a patch (smile). Then you might include a pointer in reference?
> First draft of Phoenix Tuning Guide
> ---
>
reat here. I would
want to detract from that.
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
>
://hbase.apache.org/book.html
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
> Issue Type: Impr
All,
I've uploaded a draft of the Phoenix Tuning Guide as an attachment to the
following Jira:
https://issues.apache.org/jira/browse/PHOENIX-3218
I welcome any feedback or comments.
Thanks,
Peter
Peter Conrad
Staff Technical Writer: Infrastructure | salesforce.com
Office: (415) 471
dev and user list soliciting feedback on it.
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
>
ewed and added to the website?
> First draft of Phoenix Tuning Guide
> ---
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
>
[
https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Conrad updated PHOENIX-3218:
--
Attachment: Phoenix-Tuning-Guide.md
> First draft of Phoenix Tuning Gu
Peter Conrad created PHOENIX-3218:
-
Summary: First draft of Phoenix Tuning Guide
Key: PHOENIX-3218
URL: https://issues.apache.org/jira/browse/PHOENIX-3218
Project: Phoenix
Issue Type
40 matches
Mail list logo
