[Improvement](datatype) Update Parser for IPv4/v6 data types#29044
[Improvement](datatype) Update Parser for IPv4/v6 data types#29044morningman merged 3 commits intoapache:masterfrom
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
run buildall |
|
run arm |
|
TeamCity be ut coverage result: |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
|
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
run p0 |
|
run buildall |
|
TeamCity be ut coverage result: |
|
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
|
run PipelineX |
|
run pipelinex_p0 |
1 similar comment
|
run pipelinex_p0 |
sjyango
force-pushed
the
ip-parser
branch
2 times, most recently
from
db55e88 to
941d67d
Compare
|
run buildall |
|
TeamCity be ut coverage result: |
|
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
|
run buildall |
|
TeamCity be ut coverage result: |
|
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
|
run p0 |
|
PR approved by anyone and no changes requested. |
github-actions
bot
added
the
approved
|
PR approved by at least one committer and no changes requested. |
…29044) Transforming from parsing std:: string to parsing char * to accelerate the parsing of ipv4/v6 data types.
…29044) Transforming from parsing std:: string to parsing char * to accelerate the parsing of ipv4/v6 data types.
…29044) Transforming from parsing std:: string to parsing char * to accelerate the parsing of ipv4/v6 data types.
4 participants
Proposed changes
Transforming from parsing std:: string to parsing char * to accelerate the parsing of ipv4/v6 data types.
Comparison of import speed improvement for stream load:
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...